Local privilege escalation via unchecked mtee write
Published Apr 6, 2023 · Updated Mar 17, 2025
Out-of-bounds write in mtee on MediaTek chipsets running Android 10.0 through 13.0 allows local users to elevate privileges. The mtee component performs a write without the required bounds check, allowing data to be written beyond the intended buffer. Exploitation requires System execution privileges and no user interaction; MediaTek has not disclosed the affected function or input path.
Summary
What happened
Out-of-bounds write in mtee on MediaTek chipsets running Android 10.0 through 13.0 allows local users to elevate privileges. The mtee component performs a write without the required bounds check, allowing data to be written beyond the intended buffer. Exploitation requires System execution privileges and no user interaction; MediaTek has not disclosed the affected function or input path.
The record
- CVE
- CVE-2023-20657
- Published
- Apr 6, 2023
- Updated
- Mar 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 6, 2023CVE publishedPublication date reported by the CVE source.
- Mar 17, 2025Record 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.
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