Remote code execution via unchecked firmware write
Published Dec 16, 2022 · Updated Apr 18, 2025
An out-of-bounds write in Android Pixel cellular firmware allows remote attackers to execute code through an LTE-authenticated connection. The firmware omits a bounds check before performing a write, allowing data to extend beyond its intended buffer; Google has not disclosed the affected function or message format. Exploitation requires LTE authentication but no user interaction, and successful exploitation executes code in the cellular firmware context.
Summary
What happened
An out-of-bounds write in Android Pixel cellular firmware allows remote attackers to execute code through an LTE-authenticated connection. The firmware omits a bounds check before performing a write, allowing data to extend beyond its intended buffer; Google has not disclosed the affected function or message format. Exploitation requires LTE authentication but no user interaction, and successful exploitation executes code in the cellular firmware context.
The record
- CVE
- CVE-2022-20607
- Published
- Dec 16, 2022
- Updated
- Apr 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 18, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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