Local privilege escalation via unchecked FIQ request
Published Sep 14, 2022 · Updated Aug 3, 2024
Out-of-bounds write in Google Trusty's Android kernel ARM GIC code allows local users to elevate privileges without interaction. The smc_intc_request_fiq function in arm_gic.c fails to validate input before writing outside the intended bounds. System execution privileges are required, and successful exploitation can compromise confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in Google Trusty's Android kernel ARM GIC code allows local users to elevate privileges without interaction. The smc_intc_request_fiq function in arm_gic.c fails to validate input before writing outside the intended bounds. System execution privileges are required, and successful exploitation can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2022-20231
- Published
- Sep 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Product
- Trusty
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 14, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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