Local information disclosure via missing null check
Published Apr 5, 2024 · Updated Nov 5, 2024
Out-of-bounds read in the Google Android kernel allows local users to disclose information without user interaction or additional execution privileges. asn1_ec_pkey_parse_p384 in asn1_common.c fails to check a parsing value for null before using it, causing an out-of-bounds read. A local low-privileged process can obtain kernel-resident information, with no reported write, code-execution, or service-interruption impact.
Summary
What happened
Out-of-bounds read in the Google Android kernel allows local users to disclose information without user interaction or additional execution privileges. asn1_ec_pkey_parse_p384 in asn1_common.c fails to check a parsing value for null before using it, causing an out-of-bounds read. A local low-privileged process can obtain kernel-resident information, with no reported write, code-execution, or service-interruption impact.
The record
- CVE
- CVE-2024-29751
- Published
- Apr 5, 2024
- Updated
- Nov 5, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2024CVE publishedPublication date reported by the CVE source.
- Nov 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?
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?
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