Remote privilege escalation via scratch allocator overflow
Published May 14, 2020 · Updated Aug 4, 2024
Integer overflow in Android kernel Airbrush firmware allows remote attackers to elevate privileges through crafted allocations. The scratch-memory allocator fails to detect numeric overflow when calculating an allocation, so a subsequent allocation can return a pointer into memory owned by the preceding allocation. No authentication or user interaction is required, and overlapping allocations enable improper memory access within the Airbrush firmware context.
Summary
What happened
Integer overflow in Android kernel Airbrush firmware allows remote attackers to elevate privileges through crafted allocations. The scratch-memory allocator fails to detect numeric overflow when calculating an allocation, so a subsequent allocation can return a pointer into memory owned by the preceding allocation. No authentication or user interaction is required, and overlapping allocations enable improper memory access within the Airbrush firmware context.
The record
- CVE
- CVE-2020-0221
- Published
- May 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-682, T1404
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 kernel
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