Local privilege escalation via aee stack overflow
Published Feb 2, 2021 · Updated Aug 3, 2024
Stack buffer overflow in the aee component of Google Cloud Android 11 allows local users to gain System execution privileges. The component writes beyond a stack buffer while processing undisclosed local input, corrupting memory; neither the affected routine nor the missing bounds operation is public. Exploitation requires existing System execution privileges and needs no user interaction, limiting exposure to code already running locally on an affected device.
Summary
What happened
Stack buffer overflow in the aee component of Google Cloud Android 11 allows local users to gain System execution privileges. The component writes beyond a stack buffer while processing undisclosed local input, corrupting memory; neither the affected routine nor the missing bounds operation is public. Exploitation requires existing System execution privileges and needs no user interaction, limiting exposure to code already running locally on an affected device.
The record
- CVE
- CVE-2021-0362
- Published
- Feb 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 2, 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-11
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