Memory disclosure via get_kek read-after-free
Published Apr 8, 2020 · Updated Aug 5, 2024
A race condition in get_kek on Samsung mobile devices with Android 5.1, 6.0, and 7.x allows remote attackers to read freed memory. The get_kek routine accesses an object after another execution path frees it because concurrent access is not properly synchronized. Successful exploitation requires winning the timing race; Samsung has not published which memory can be read or any further consequence.
Summary
What happened
A race condition in get_kek on Samsung mobile devices with Android 5.1, 6.0, and 7.x allows remote attackers to read freed memory. The get_kek routine accesses an object after another execution path frees it because concurrent access is not properly synchronized. Successful exploitation requires winning the timing race; Samsung has not published which memory can be read or any further consequence.
The record
- CVE
- CVE-2018-21084
- Published
- Apr 8, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, CWE-362
- Attack vector
- network
- Privileges
- unauthenticated
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.
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