HMAC verification timing leak via early-exit comparison
Published Feb 11, 2024 · Updated Aug 1, 2024
Timing side channel in Rhonabwy 1.1.13 and earlier allows remote attackers to infer HMAC comparison progress during JWS verification. The r_jws_verify_sig_hmac function in src/jws.c compares supplied and computed Base64url signatures with an early-exit string comparison instead of constant-time logic. Repeated access to an application exposing HMAC verification is required, and response timing serves as an oracle for signature guesses rather than directly exposing payload data.
Summary
What happened
Timing side channel in Rhonabwy 1.1.13 and earlier allows remote attackers to infer HMAC comparison progress during JWS verification. The r_jws_verify_sig_hmac function in src/jws.c compares supplied and computed Base64url signatures with an early-exit string comparison instead of constant-time logic. Repeated access to an application exposing HMAC verification is required, and response timing serves as an oracle for signature guesses rather than directly exposing payload data.
The record
- CVE
- CVE-2024-25714
- Published
- Feb 11, 2024
- Updated
- Aug 1, 2024
- Vendor
- Babelouest
- Product
- Rhonabwy
- Classifications
- CWE-1255, CWE-203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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.1.13
What conditions does exploitation require?
What is affected?
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