Local privilege escalation via unchecked annotation count
Published Jul 9, 2024 · Updated Aug 2, 2024
Out-of-bounds write in Google Android 12, 12L, 13, and 14 allows local users to escalate privileges through a crafted StatsEvent. increment_annotation_count in stats_event.c increments annotation storage without first checking whether the event buffer has enough space, permitting a heap-buffer overflow. A local app can reach the affected StatsD library without additional execution privileges or user interaction, and successful memory corruption grants elevated privileges.
Summary
What happened
Out-of-bounds write in Google Android 12, 12L, 13, and 14 allows local users to escalate privileges through a crafted StatsEvent. increment_annotation_count in stats_event.c increments annotation storage without first checking whether the event buffer has enough space, permitting a heap-buffer overflow. A local app can reach the affected StatsD library without additional execution privileges or user interaction, and successful memory corruption grants elevated privileges.
The record
- CVE
- CVE-2024-31311
- Published
- Jul 9, 2024
- Updated
- Aug 2, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-269, CWE-787, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <12
- Affected versionversion=12
- Affected versionversion=12L
- Affected versionversion=13
- Affected versionversion=14
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