GHSA-jv3g-j58f-9mq9
MEDIUMJOSE vulnerable to resource exhaustion via specifically crafted JWE
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
josenpmjose-node-cjs-runtimenpmDescription
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+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
keyManagementAlgorithmsdecryption option not including any of the PBKDF2-based JWE key management algorithms
Patches
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.
- they can use the
keyManagementAlgorithmsdecryption option to disable accepting PBKDF2 altogether - they can inspect the JOSE Header prior to using the decryption API and limit the PBKDF2 iteration count (
p2cHeader 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]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦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 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jose. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update jose to 1.28.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jv3g-j58f-9mq9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jv3g-j58f-9mq9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-jv3g-j58f-9mq9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jv3g-j58f-9mq9 in your dependencies?
O3 detects GHSA-jv3g-j58f-9mq9 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.