Key-material exposure via AES-GCM T-Table cache leakage
Published Apr 8, 2020 · Updated Aug 5, 2024
Cache side channel in Samsung Keymaster on Android 7.0 and 8.0 allows attackers to observe AES-GCM key-dependent cache activity. The AES-GCM implementation uses lookup T-Tables, leaving secret-dependent memory accesses in processor-cache state instead of using the Cryptography Extension. Exposure is confined to Android 7.0 devices with Exynos 7420 and Android 8.0 devices with Exynos 8890 or 8996 chipsets.
Summary
What happened
Cache side channel in Samsung Keymaster on Android 7.0 and 8.0 allows attackers to observe AES-GCM key-dependent cache activity. The AES-GCM implementation uses lookup T-Tables, leaving secret-dependent memory accesses in processor-cache state instead of using the Cryptography Extension. Exposure is confined to Android 7.0 devices with Exynos 7420 and Android 8.0 devices with Exynos 8890 or 8996 chipsets.
The record
- CVE
- CVE-2018-21058
- Published
- Apr 8, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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