CVE-2022-36083

MEDIUM
Published Sep 7, 20223y ago · Modified Jun 22, 20261w ago
5.3 CVSS 3.1
Medium
Find Similar
Published Sep 7, 2022 3y ago
Last Modified Jun 22, 2026 1w ago

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

CVSS Details

Base Score
5.3
Exploitability
3.9
Impact
1.4
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Attack Vector Network
Attack Complexity Low
Privileges Required None
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability Low

Threat Intelligence

No active exploitation signals — not in CISA KEV and no EPSS score yet.

Exploit & Patch Status
Public Exploit Known
Patch Available

Weaknesses 2

CWE-400 Uncontrolled Resource Consumption Resource Mgmt
CWE-834

Affected Products 4

VendorProductVersionRange
panvajose*≥1.0.0  –  <1.28.2
panvajose*≥2.0.0  –  <2.0.6
panvajose*≥3.0.0  –  <3.20.4
panvajose*≥4.0.0  –  <4.9.2

References 3

  • github.com https://github.com/panva/jose/commit/03d6d013bf6e070e85adfe5731f526978e3e8e4d
    PatchThird Party Advisory
  • github.com https://github.com/panva/jose/releases/tag/v4.9.2
    Third Party Advisory
  • github.com https://github.com/panva/jose/security/advisories/GHSA-jv3g-j58f-9mq9
    ExploitThird Party Advisory

Remediation

  • github.com https://github.com/panva/jose/commit/03d6d013bf6e070e85adfe5731f526978e3e8e4d
    PatchThird Party Advisory