Local privilege escalation via incorrect bounds check
Published Mar 24, 2023 · Updated Feb 20, 2025
Out-of-bounds read in imsservice.cpp in the Android kernel allows local users with System privileges to escalate privileges without interaction. DoSetTempEcc applies an incorrect bounds check before reading memory, while Google identifies the affected Pixel subcomponent as rild_exynos. Exploitation requires local System execution privileges; the public bulletin does not disclose the crafted input or resulting privilege boundary.
Summary
What happened
Out-of-bounds read in imsservice.cpp in the Android kernel allows local users with System privileges to escalate privileges without interaction. DoSetTempEcc applies an incorrect bounds check before reading memory, while Google identifies the affected Pixel subcomponent as rild_exynos. Exploitation requires local System execution privileges; the public bulletin does not disclose the crafted input or resulting privilege boundary.
The record
- CVE
- CVE-2023-21062
- Published
- Mar 24, 2023
- Updated
- Feb 20, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-125, T1068
- Attack vector
- local
- Privileges
- admin
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