Local privilege escalation via use-after-free
Published Nov 18, 2021 · Updated Aug 3, 2024
Use-after-free memory corruption in MediaTek APUSYS on Android 10.0 and 11.0 allows local users to escalate privileges to System. MediaTek identifies APUSYS as the affected locus but has not published the object lifetime error, entry point, or operation that accesses freed memory. Exploitation requires local System execution privileges and no user interaction; successful exploitation corrupts memory to elevate privilege.
Summary
What happened
Use-after-free memory corruption in MediaTek APUSYS on Android 10.0 and 11.0 allows local users to escalate privileges to System. MediaTek identifies APUSYS as the affected locus but has not published the object lifetime error, entry point, or operation that accesses freed memory. Exploitation requires local System execution privileges and no user interaction; successful exploitation corrupts memory to elevate privilege.
The record
- CVE
- CVE-2021-0667
- Published
- Nov 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- MediaTek
- Product
- MediaTek APUSYS
- Classifications
- CWE-416, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 18, 2021CVE 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 10.0, 11.0
What conditions does exploitation require?
What is affected?
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