Local privilege escalation via vdec bounds-check omission
Published Dec 2, 2024 · Updated Dec 3, 2024
Out-of-bounds write in MediaTek vdec on affected Android 13.0 and 14.0 chipsets allows local users to escalate privileges. The vdec component omits a bounds check before a write, allowing data to be written beyond its intended buffer. Exploitation requires prior System privilege and no user interaction; successful memory corruption grants higher local privileges.
Summary
What happened
Out-of-bounds write in MediaTek vdec on affected Android 13.0 and 14.0 chipsets allows local users to escalate privileges. The vdec component omits a bounds check before a write, allowing data to be written beyond its intended buffer. Exploitation requires prior System privilege and no user interaction; successful memory corruption grants higher local privileges.
The record
- CVE
- CVE-2024-20125
- Published
- Dec 2, 2024
- Updated
- Dec 3, 2024
- Vendor
- MediaTek
- Product
- MT8175
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Dec 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=0 <=*
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