Local privilege escalation via ACPM bounds-check omission
Published Mar 11, 2024 · Updated Aug 27, 2024
Out-of-bounds write in Android 13's ACPM component allows local users to elevate privileges without user interaction. The private Android bug does not disclose the affected function or input, but Google attributes the write to a missing bounds check in ACPM. Exploitation requires local code execution but no additional execution privileges, and successful corruption grants elevated access.
Summary
What happened
Out-of-bounds write in Android 13's ACPM component allows local users to elevate privileges without user interaction. The private Android bug does not disclose the affected function or input, but Google attributes the write to a missing bounds check in ACPM. Exploitation requires local code execution but no additional execution privileges, and successful corruption grants elevated access.
The record
- CVE
- CVE-2024-27208
- Published
- Mar 11, 2024
- Updated
- Aug 27, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=13
- Affected versionversion=13.0
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.
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