Local privilege escalation via String16 length overflow
Published Nov 27, 2024 · Updated Nov 29, 2024
Out-of-bounds write in String16.cpp in Google Android 6.0 through 8.1 and Pixel devices allows local users to elevate privileges. String16 allocation and append paths calculate UTF-16 buffer sizes without overflow checks, then copy or terminate data using the original lengths. Exploitation runs from an unprivileged local process without user interaction and can execute with elevated privileges.
Summary
What happened
Out-of-bounds write in String16.cpp in Google Android 6.0 through 8.1 and Pixel devices allows local users to elevate privileges. String16 allocation and append paths calculate UTF-16 buffer sizes without overflow checks, then copy or terminate data using the original lengths. Exploitation runs from an unprivileged local process without user interaction and can execute with elevated privileges.
The record
- CVE
- CVE-2017-13323
- Published
- Nov 27, 2024
- Updated
- Nov 29, 2024
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-787, CWE-190, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 29, 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 <2018-05-05
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