jose
Affected
- introduced
1.0.0, fixed1.28.2(semver)
Fixed versions
1.28.2
Fix
- Fixed version
1.28.2npm install [email protected]
Advisory
Also known as: CVE-2022-36083
JOSE vulnerable to resource exhaustion via specifically crafted JWE
The PBKDF2-based JWE key management algorithms expect a JOSE Header Parameter named p2c (PBES2 Count), which determines how many PBKDF2 iterations must be executed in order to derive a CEK wrapping key. The purpose of this parameter is to intentionally slow down the key derivation function in order to make password brute-force and dictionary attacks more expensive.
This makes the PBES2 algorithms unsuitable for situations where the JWE is coming from an untrusted source: an adversary can intentionally pick an extremely high PBES2 Count value, that will initiate a CPU-bound computation that may take an unreasonable amount of time to finish.
Impact
Under certain conditions (see below) it is possible to have the user's environment consume unreasonable amount of CPU time.
Affected users
The impact is limited only to users utilizing the JWE decryption APIs with symmetric secrets to decrypt JWEs from untrusted parties who do not limit the accepted JWE Key Management Algorithms (alg Header Parameter) using the keyManagementAlgorithms (or algorithms in v1.x) decryption option or through other means.
The PBKDF2-based JWE Key Management Algorithm Identifiers are
PBES2-HS256+A128KWPBES2-HS384+A192KWPBES2-HS512+A256KWe.g.
const secret = new Uint8Array(16)
const jwe = '...' // JWE from an untrusted party
await jose.compactDecrypt(jwe, secret)
You are NOT affected if any of the following applies to you
keyManagementAlgorithms decryption option not including any of the PBKDF2-based JWE key management algorithmsPatches
v1.28.2, v2.0.6, v3.20.4, and v4.9.2 releases limit the maximum PBKDF2 iteration count to 10000 by default. It is possible to adjust this limit with a newly introduced maxPBES2Count decryption option.
Workarounds
All users should be able to upgrade given all stable semver major release lines have had new a patch release introduced which limits the PBKDF2 iteration count to 10000 by default. This removes the ability to craft JWEs that would consume unreasonable amount of CPU time.
If users are unable to upgrade their required library version they have two options depending on whether they expect to receive JWEs using any of the three PBKDF2-based JWE key management algorithms.
keyManagementAlgorithms decryption option to disable accepting PBKDF2 altogetherp2c Header Parameter)For more information
If you have any questions or comments about this advisory:
Medium Basis: The source's own band: MODERATE
1.0.0, fixed 1.28.2 (semver)1.28.2
1.28.2npm install [email protected]3.0.0, fixed 3.20.4 (semver)3.20.4
3.20.4npm install [email protected]3.0.0, fixed 3.20.4 (semver)3.20.4
3.20.4npm install [email protected]3.0.0, fixed 3.20.4 (semver)3.20.4
3.20.4npm install [email protected]2.0.0, fixed 2.0.6 (semver)2.0.6
2.0.6npm install [email protected]3.0.0, fixed 3.20.4 (semver)3.20.4
3.20.4npm install [email protected]4.0.0, fixed 4.9.2 (semver)4.9.2
4.9.2npm install [email protected]4.0.0, fixed 4.9.2 (semver)4.9.2
4.9.2npm install [email protected]4.0.0, fixed 4.9.2 (semver)4.9.2
4.9.2npm install [email protected]4.0.0, fixed 4.9.2 (semver)4.9.2
4.9.2npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0