Local privilege escalation via active debug code
Published May 3, 2022 · Updated Aug 3, 2024
Memory corruption in the MediaTek aee driver on Android 11.0 and 12.0 allows local users to escalate privileges from a System context. MediaTek has not disclosed which debug path remains active or how its memory operations become corrupt. Exploitation requires local access and existing System execution privileges, needs no user interaction, and can elevate the attacking process to an unspecified higher privilege level.
Summary
What happened
Memory corruption in the MediaTek aee driver on Android 11.0 and 12.0 allows local users to escalate privileges from a System context. MediaTek has not disclosed which debug path remains active or how its memory operations become corrupt. Exploitation requires local access and existing System execution privileges, needs no user interaction, and can elevate the attacking process to an unspecified higher privilege level.
The record
- CVE
- CVE-2022-20089
- Published
- May 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-489, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 3, 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.
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