System privilege escalation via unchecked SIM parsing
Published Dec 16, 2022 · Updated Apr 18, 2025
Out-of-bounds write in Android rild_exynos allows local users with System privileges to escalate privileges without user interaction. FacilityLock::Parse in simdata.cpp parses facility-lock SIM data without checking destination bounds, permitting memory writes outside the intended buffer. The path is limited to supported Pixel devices using the affected Exynos radio daemon and requires existing System execution privileges.
Summary
What happened
Out-of-bounds write in Android rild_exynos allows local users with System privileges to escalate privileges without user interaction. FacilityLock::Parse in simdata.cpp parses facility-lock SIM data without checking destination bounds, permitting memory writes outside the intended buffer. The path is limited to supported Pixel devices using the affected Exynos radio daemon and requires existing System execution privileges.
The record
- CVE
- CVE-2022-42502
- Published
- Dec 16, 2022
- Updated
- Apr 18, 2025
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
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?
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