AES key inference via S-box cache timing
Published Aug 22, 2024 · Updated Sep 10, 2024
Cache-timing exposure in Matrix.org Olm 3.2.16 and earlier allows attackers to infer AES key material through timing measurements. Olm's bundled AES implementation indexes secret-dependent S-box lookup tables during the SubWord step, allowing cache behavior to vary with processed key data. Practical recovery requires precise repeated observations against the same short-lived key material; Matrix.org reports network exploitation is infeasible and only a local attack appears plausible.
Summary
What happened
Cache-timing exposure in Matrix.org Olm 3.2.16 and earlier allows attackers to infer AES key material through timing measurements. Olm's bundled AES implementation indexes secret-dependent S-box lookup tables during the SubWord step, allowing cache behavior to vary with processed key data. Practical recovery requires precise repeated observations against the same short-lived key material; Matrix.org reports network exploitation is infeasible and only a local attack appears plausible.
The record
- CVE
- CVE-2024-45191
- Published
- Aug 22, 2024
- Updated
- Sep 10, 2024
- Vendor
- Matrix.org
- Product
- Olm
- Classifications
- CWE-208
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 22, 2024CVE publishedPublication date reported by the CVE source.
- Sep 10, 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 <=3.2.16
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