CPU exhaustion via unbounded PBES2 iteration count
Published Dec 4, 2023 · Updated May 29, 2025
Uncontrolled resource consumption in lestrrat-go jwx before 1.2.27 and 2.0.0 through 2.0.17 allows remote attackers to exhaust CPU. The JWE decrypt path accepts an attacker-controlled PBES2 p2c count and passes it to PBKDF2 without a maximum, forcing excessive key-derivation iterations. Exposure requires an application to decrypt attacker-supplied JWE; JWT signature verification alone does not reach the affected path.
Summary
What happened
Uncontrolled resource consumption in lestrrat-go jwx before 1.2.27 and 2.0.0 through 2.0.17 allows remote attackers to exhaust CPU. The JWE decrypt path accepts an attacker-controlled PBES2 p2c count and passes it to PBKDF2 without a maximum, forcing excessive key-derivation iterations. Exposure requires an application to decrypt attacker-supplied JWE; JWT signature verification alone does not reach the affected path.
The record
- CVE
- CVE-2023-49290
- Published
- Dec 4, 2023
- Updated
- May 29, 2025
- Vendor
- lestrrat-go
- Product
- jwx
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- May 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.27
- Affected versionversion=>= 2.0.0, < 2.0.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream malicious-p2c JWE proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo