Remote code execution via PAC parser overflow
Published Mar 10, 2021 · Updated Aug 3, 2024
Out-of-bounds write in V8 Scanner::LiteralBuffer::NewCapacity in Android 8.1 through 11 allows attackers to execute code via malicious PAC files. Integer-overflow arithmetic miscomputes the buffer capacity before growth, causing a write outside the allocated literal buffer. Exploitation requires a crafted PAC file to reach Android's parser and does not require additional execution privileges or user interaction.
Summary
What happened
Out-of-bounds write in V8 Scanner::LiteralBuffer::NewCapacity in Android 8.1 through 11 allows attackers to execute code via malicious PAC files. Integer-overflow arithmetic miscomputes the buffer capacity before growth, causing a write outside the allocated literal buffer. Exploitation requires a crafted PAC file to reach Android's parser and does not require additional execution privileges or user interaction.
The record
- CVE
- CVE-2021-0393
- Published
- Mar 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, CWE-190, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 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 Android-8.1 Android-9 Android-10
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