Remote code execution via unchecked TCP SACK option
Published Mar 24, 2023 · Updated Feb 21, 2025
Out-of-bounds write in Android cellular firmware allows remote attackers to execute code by sending a crafted TCP SACK option. ProfSixDecomTcpSACKoption in RohcPacketCommon processes the option without a bounds check and writes past the destination buffer. No privileges or user interaction are required, and Google has not disclosed the affected Pixel models or the cellular path needed to reach the parser.
Summary
What happened
Out-of-bounds write in Android cellular firmware allows remote attackers to execute code by sending a crafted TCP SACK option. ProfSixDecomTcpSACKoption in RohcPacketCommon processes the option without a bounds check and writes past the destination buffer. No privileges or user interaction are required, and Google has not disclosed the affected Pixel models or the cellular path needed to reach the parser.
The record
- CVE
- CVE-2023-21057
- Published
- Mar 24, 2023
- Updated
- Feb 21, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 21, 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?
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
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