CPU exhaustion via unbounded PBES2 iteration count
Published Mar 19, 2024 · Updated Aug 2, 2024
Resource exhaustion in potatosalad JOSE 1.11.6 and earlier allows remote attackers to interrupt service via a crafted JOSE header. The JWE PBES2 key-unwrapping path accepts the header's p2c value as the PBKDF2 iteration count without an upper bound, consuming excessive CPU. Any application that decrypts attacker-controlled PBES2-encrypted JWE input can become unresponsive without authentication or user interaction.
Summary
What happened
Resource exhaustion in potatosalad JOSE 1.11.6 and earlier allows remote attackers to interrupt service via a crafted JOSE header. The JWE PBES2 key-unwrapping path accepts the header's p2c value as the PBKDF2 iteration count without an upper bound, consuming excessive CPU. Any application that decrypts attacker-controlled PBES2-encrypted JWE input can become unresponsive without authentication or user interaction.
The record
- CVE
- CVE-2023-50966
- Published
- Mar 19, 2024
- Updated
- Aug 2, 2024
- Vendor
- potatosalad
- Product
- JOSE
- Classifications
- CWE-400, T1496.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=0 <1.11.6
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.
Public exploit references
- erlang-jose large-p2c 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