Denial of Service (DoS) Affecting @discordjs/opus package, versions <0.8.0

@discordjs/opus is a native bindings to libopus.

Affected versions of this package are vulnerable to Denial of Service (DoS) when trying to encode using an encoder with zero channels, or a non-initialized buffer. This leads to a hard crash.

// Zero channels:

const { OpusEncoder } = require('@discordjs/opus');
 const encoder = new OpusEncoder(48000, 0);
 try {
     const encoded = encoder.encode(Buffer.from("aaa"));
 } catch(e) {
console.log("This will never run")
     // never executed because of the hard crash
 }

// Non-initialized buffer:

const { OpusEncoder } = require('@discordjs/opus');
const encoder = new OpusEncoder(48000, 2);
try {
     const encoded = encoder.encode(null);
} catch(e) {
// never executed because of the hard crash
}

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

• High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

• Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

• Github Commit
• GitHub Issues
• Github PR
• Vulnerable Code