Local privilege escalation via incorrect bounds check
Published Dec 4, 2024 · Updated Dec 5, 2024
Out-of-bounds write in the Android touchscreen kernel allows local users with System privileges to escalate privileges without interaction. The store_cmd handler in ftm4_pdc.c applies an incorrect bounds check before writing command data, allowing a write beyond the intended buffer. Exploitation requires existing System execution privileges and the affected touchscreen kernel component; the bounded impact is privilege escalation.
Summary
What happened
Out-of-bounds write in the Android touchscreen kernel allows local users with System privileges to escalate privileges without interaction. The store_cmd handler in ftm4_pdc.c applies an incorrect bounds check before writing command data, allowing a write beyond the intended buffer. Exploitation requires existing System execution privileges and the affected touchscreen kernel component; the bounded impact is privilege escalation.
The record
- CVE
- CVE-2018-9462
- Published
- Dec 4, 2024
- Updated
- Dec 5, 2024
- Vendor
- Product
- Google Pixel
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 4, 2024CVE publishedPublication date reported by the CVE source.
- Dec 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=0 <2018-08-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.
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