Secret-key disclosure via compiler-induced timing branch
Published Jun 10, 2024 · Updated Aug 2, 2024
Timing side channel in Open Quantum Safe liboqs before 0.10.1 allows remote attackers to recover ML-KEM 512 secret keys. Clang 15 through 18 converts the bit selection in the Kyber reference poly_frommsg function into secret-dependent control flow under affected optimization settings. Exposure requires an x86 build containing that reference code and repeated end-to-end decapsulation timing measurements.
Summary
What happened
Timing side channel in Open Quantum Safe liboqs before 0.10.1 allows remote attackers to recover ML-KEM 512 secret keys. Clang 15 through 18 converts the bit selection in the Kyber reference poly_frommsg function into secret-dependent control flow under affected optimization settings. Exposure requires an x86 build containing that reference code and repeated end-to-end decapsulation timing measurements.
The record
- CVE
- CVE-2024-36405
- Published
- Jun 10, 2024
- Updated
- Aug 2, 2024
- Vendor
- Open Quantum Safe
- Product
- liboqs
- Classifications
- CWE-385, CWE-208
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 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 <=0.10.0
- Affected versionversion=< 0.10.1
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