Local privilege escalation via unhandled btif errors
Published Mar 9, 2022 · Updated Aug 3, 2024
Memory corruption in btif on MediaTek chipsets running Android 11.0 or 12.0 allows local users to escalate privileges. The btif component detects an error condition but fails to act on it, leaving a memory state that can become corrupted. Exploitation requires existing System execution privileges and user interaction, and the resulting privilege gain is local to the device.
Summary
What happened
Memory corruption in btif on MediaTek chipsets running Android 11.0 or 12.0 allows local users to escalate privileges. The btif component detects an error condition but fails to act on it, leaving a memory state that can become corrupted. Exploitation requires existing System execution privileges and user interaction, and the resulting privilege gain is local to the device.
The record
- CVE
- CVE-2022-20057
- Published
- Mar 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-390, CWE-755, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 9, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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