Modem code execution via 2G ASN.1 overflow
Published Jun 15, 2022 · Updated Aug 3, 2024
Heap buffer overflow in the Android modem stack allows physically proximate attackers to execute code through crafted 2G call setup data. The ASN.1 parser allocates a one-byte heap buffer, accepts an attacker-controlled length of up to 255 bytes, and writes that amount into the allocation. Exploitation requires a Pixel 6 with 2G enabled and a malicious base station within radio range; the flaw corrupts adjacent heap objects and was chained with a separate executable-memory misconfiguration for total modem compromise.
Summary
What happened
Heap buffer overflow in the Android modem stack allows physically proximate attackers to execute code through crafted 2G call setup data. The ASN.1 parser allocates a one-byte heap buffer, accepts an attacker-controlled length of up to 255 bytes, and writes that amount into the allocation. Exploitation requires a Pixel 6 with 2G enabled and a malicious base station within radio range; the flaw corrupts adjacent heap objects and was chained with a separate executable-memory misconfiguration for total modem compromise.
The record
- CVE
- CVE-2022-20170
- Published
- Jun 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2022CVE 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 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.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Pixel modem RCE proof of conceptfunctional · demonstrated
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