Kernel information disclosure via missing bounds check
Published Jun 22, 2021 · Updated Aug 3, 2024
Out-of-bounds read in the Android kernel allows local users with System execution privileges to disclose kernel information. The pfkey_dump function in af_key.c reads beyond a valid buffer because it does not perform the required bounds check before accessing memory. Exploitation requires System execution privileges and no user interaction, and the reported impact is limited to kernel information disclosure.
Summary
What happened
Out-of-bounds read in the Android kernel allows local users with System execution privileges to disclose kernel information. The pfkey_dump function in af_key.c reads beyond a valid buffer because it does not perform the required bounds check before accessing memory. Exploitation requires System execution privileges and no user interaction, and the reported impact is limited to kernel information disclosure.
The record
- CVE
- CVE-2021-0605
- Published
- Jun 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Android kernel
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