Local privilege escalation via missing VPU bounds check
Published Feb 4, 2021 · Updated Aug 3, 2024
An out-of-bounds write in Android 9 through 11 VPU code allows local users with System execution privileges to escalate privileges. The VPU component writes outside a buffer because it fails to validate an unspecified input boundary before the write. Exploitation requires existing System execution privileges on the device, but no user interaction; public records do not identify the input or affected function.
Summary
What happened
An out-of-bounds write in Android 9 through 11 VPU code allows local users with System execution privileges to escalate privileges. The VPU component writes outside a buffer because it fails to validate an unspecified input boundary before the write. Exploitation requires existing System execution privileges on the device, but no user interaction; public records do not identify the input or affected function.
The record
- CVE
- CVE-2021-0348
- Published
- Feb 4, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 4, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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-9, Android-10, Android-11
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