CVE-2022-36083

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.

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+A128KW
• PBES2-HS384+A192KW
• PBES2-HS512+A256KW

e.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

• Your code does not use the JWE APIs
• Your code only produces JWE tokens
• Your code only decrypts JWEs using an asymmetric JWE Key Management Algorithm (this means you're providing an asymmetric key object to the JWE decryption API)
• Your code only accepts JWEs produced by trusted sources
• Your code limits the accepted JWE Key Management Algorithms using the keyManagementAlgorithms decryption option not including any of the PBKDF2-based JWE key management algorithms

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.

• they can use the keyManagementAlgorithms decryption option to disable accepting PBKDF2 altogether
• they can inspect the JOSE Header prior to using the decryption API and limit the PBKDF2 iteration count (p2c Header Parameter)

For more information

If you have any questions or comments about this advisory:

• Open an discussion in the project's repository
• Email me at [email protected]

Under certain conditions (see below) it is possible to have the user's environment consume unreasonable amount of CPU time.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2022-36083 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.28.2, 3.20.4, 2.0.6, 4.9.2); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2022-36083? CVE-2022-36083 is a medium-severity uncontrolled resource consumption vulnerability in jose (npm), affecting versions >= 1.0.0, <= 1.28.1. It is fixed in 1.28.2, 3.20.4, 2.0.6, 4.9.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2022-36083? CVE-2022-36083 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-36083?
   • jose (npm) (versions >= 1.0.0, <= 1.28.1)
   • jose-browser-runtime (npm) (versions >= 3.0.0, <= 3.20.3)
   • jose-node-cjs-runtime (npm) (versions >= 3.0.0, <= 3.20.3)
   • jose-node-esm-runtime (npm) (versions >= 3.0.0, <= 3.20.3)
4. Is there a fix for CVE-2022-36083? Yes. CVE-2022-36083 is fixed in 1.28.2, 3.20.4, 2.0.6, 4.9.2. Upgrade to this version or later.
5. Is CVE-2022-36083 exploitable, and should I be worried? Whether CVE-2022-36083 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-36083 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-36083?
   • Upgrade jose to 1.28.2 or later
   • Upgrade jose-browser-runtime to 3.20.4 or later
   • Upgrade jose-node-cjs-runtime to 3.20.4 or later
   • Upgrade jose-node-esm-runtime to 3.20.4 or later
   • Upgrade jose to 2.0.6 or later
   • Upgrade jose to 3.20.4 or later
   • Upgrade jose to 4.9.2 or later
   • Upgrade jose-browser-runtime to 4.9.2 or later
   • Upgrade jose-node-cjs-runtime to 4.9.2 or later
   • Upgrade jose-node-esm-runtime to 4.9.2 or later