Resource Exhaustion Affecting jose package, versions <2.0.7 >=3.0.0 <4.15.5

jose is an Universal 'JSON Web Almost Everything' - JWA, JWS, JWE, JWT, JWK with no dependencies

Affected versions of this package are vulnerable to Resource Exhaustion due to the JWE decryption interfaces' support for decompressing plaintext after its decryption. An attacker can cause the application to consume an unreasonable amount of CPU time or memory by sending malicious JWE payloads with compressed plaintext.

Note:

This is only exploitable if the application uses JWE decryption from untrusted sources and runs in a Node.js environment.

This vulnerability can be mitigated by detecting and rejecting compressed JWEs early by checking the token's protected header. If zip is not undefined in the protected header, the token can be rejected to prevent exploitation.

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 Commit