Overestimated HMAC key strength via ignored characters
Published Apr 1, 2024 · Updated Aug 27, 2024
Improper key handling in JWTK JJWT 0.12.5 and earlier allows applications to accept weaker-than-expected HMAC keys. The reported setSigningKey() and signWith() paths decode string key material while ignoring certain characters, so apparent text length can overstate the effective key bytes. The condition requires application-supplied string key material; JWTK disputes that supported versions can exhibit it, and GitHub withdrew the advisory.
Summary
What happened
Improper key handling in JWTK JJWT 0.12.5 and earlier allows applications to accept weaker-than-expected HMAC keys. The reported setSigningKey() and signWith() paths decode string key material while ignoring certain characters, so apparent text length can overstate the effective key bytes. The condition requires application-supplied string key material; JWTK disputes that supported versions can exhibit it, and GitHub withdrew the advisory.
The record
- CVE
- CVE-2024-31033
- Published
- Apr 1, 2024
- Updated
- Aug 27, 2024
- Vendor
- JWTK
- Product
- JJWT
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 27, 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 <=0.12.5
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
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