Remote code execution via unchecked buffer write
Published Mar 24, 2023 · Updated Feb 20, 2025
Out-of-bounds write in Android kernel cellular firmware allows remote attackers to execute code without privileges or user interaction. The lcsm_SendRrAcquiAssist function in lcsm_bcm_assist.c fails to check a destination bound before writing, allowing input to cross the intended buffer boundary. The cellular processing path is network-reachable, and successful exploitation executes code in the affected firmware context.
Summary
What happened
Out-of-bounds write in Android kernel cellular firmware allows remote attackers to execute code without privileges or user interaction. The lcsm_SendRrAcquiAssist function in lcsm_bcm_assist.c fails to check a destination bound before writing, allowing input to cross the intended buffer boundary. The cellular processing path is network-reachable, and successful exploitation executes code in the affected firmware context.
The record
- CVE
- CVE-2023-21058
- Published
- Mar 24, 2023
- Updated
- Feb 20, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1664
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 20, 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?
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.
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