CVE-2022-36083
Description
JOSE is "JSON Web Almost Everything" - JWA, JWS, JWE, JWT, JWK, JWKS with no dependencies using runtime's native crypto in Node.js, Browser, Cloudflare Workers, Electron, and Deno. 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. Under certain conditions, it is possible to have the user's environment consume unreasonable amount of CPU time. 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 `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. 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. They can use the `keyManagementAlgorithms` decryption option to disable accepting PBKDF2 altogether, or they can inspect the JOSE Header prior to using the decryption API and limit the PBKDF2 iteration count (`p2c` Header Parameter).
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| debian | bookworm | fixed | 4.9.2-1 |
| debian | trixie | fixed | 4.9.2-1 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| npm | jose | >=1.0.0,<1.28.2 | 1.28.2 |
| npm | jose-browser-runtime | >=3.0.0,<3.20.4 | 3.20.4 |
| npm | jose-node-cjs-runtime | >=3.0.0,<3.20.4 | 3.20.4 |
| npm | jose-node-esm-runtime | >=3.0.0,<3.20.4 | 3.20.4 |
| npm | jose | >=2.0.0,<2.0.6 | 2.0.6 |
| npm | jose | >=3.0.0,<3.20.4 | 3.20.4 |
| npm | jose | >=4.0.0,<4.9.2 | 4.9.2 |
| npm | jose-browser-runtime | >=4.0.0,<4.9.2 | 4.9.2 |
| npm | jose-node-cjs-runtime | >=4.0.0,<4.9.2 | 4.9.2 |
| npm | jose-node-esm-runtime | >=4.0.0,<4.9.2 | 4.9.2 |
References
- https://github.com/panva/jose/security/advisories/GHSA-jv3g-j58f-9mq9
- https://nvd.nist.gov/vuln/detail/CVE-2022-36083
- https://github.com/panva/jose/commit/03d6d013bf6e070e85adfe5731f526978e3e8e4d
- https://github.com/panva/jose
- https://github.com/panva/jose/releases/tag/v4.9.2
- https://security-tracker.debian.org/tracker/CVE-2022-36083
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.