Service interruption via unbounded PBES2 iteration count
Published Feb 12, 2024 · Updated Feb 26, 2026
Resource exhaustion in JWCrypto before 1.5.1 allows remote attackers to interrupt services by submitting a crafted JWE. The PBES2 key-unwrapping path passes the attacker-controlled p2c header value directly to PBKDF2 without limiting its iteration count. Exposure requires an application that accepts untrusted JWE input and enables a PBES2 algorithm; each request can monopolize CPU during key derivation.
Summary
What happened
Resource exhaustion in JWCrypto before 1.5.1 allows remote attackers to interrupt services by submitting a crafted JWE. The PBES2 key-unwrapping path passes the attacker-controlled p2c header value directly to PBKDF2 without limiting its iteration count. Exposure requires an application that accepts untrusted JWE input and enables a PBES2 algorithm; each request can monopolize CPU during key derivation.
The record
- CVE
- CVE-2023-6681
- Published
- Feb 12, 2024
- Updated
- Feb 26, 2026
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2024CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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
No public exploit references are available in this record.
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