Local privilege escalation via missing bounds check
Published Dec 17, 2021 · Updated Aug 3, 2024
Out-of-bounds write in MediaTek APUSYS on Android 10.0 through 12.0 allows local users with System privileges to elevate access. The APUSYS component writes beyond a memory buffer because an input-dependent bound is not checked; MediaTek has not disclosed the affected function or data path. Exploitation requires existing System execution privileges on an affected MediaTek chipset, needs no user interaction, and can corrupt memory to elevate access.
Summary
What happened
Out-of-bounds write in MediaTek APUSYS on Android 10.0 through 12.0 allows local users with System privileges to elevate access. The APUSYS component writes beyond a memory buffer because an input-dependent bound is not checked; MediaTek has not disclosed the affected function or data path. Exploitation requires existing System execution privileges on an affected MediaTek chipset, needs no user interaction, and can corrupt memory to elevate access.
The record
- CVE
- CVE-2021-0895
- Published
- Dec 17, 2021
- Updated
- Aug 3, 2024
- Vendor
- MediaTek
- Product
- MediaTek APUSYS
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 17, 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, 12.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
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