Local privilege escalation via incorrect VCU comparison
Published May 15, 2023 · Updated Jan 24, 2025
Type confusion in MediaTek VCU on affected Android and IoT-Yocto chipsets allows local users with System privileges to gain higher privileges. An incorrect comparison in VCU produces type confusion and memory corruption; MediaTek has not disclosed the affected function or input path. Exploitation is local, requires existing System execution privileges, and needs no user interaction, so the flaw does not provide initial access.
Summary
What happened
Type confusion in MediaTek VCU on affected Android and IoT-Yocto chipsets allows local users with System privileges to gain higher privileges. An incorrect comparison in VCU produces type confusion and memory corruption; MediaTek has not disclosed the affected function or input path. Exploitation is local, requires existing System execution privileges, and needs no user interaction, so the flaw does not provide initial access.
The record
- CVE
- CVE-2023-20673
- Published
- May 15, 2023
- Updated
- Jan 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-697, CWE-843, T1404, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 15, 2023CVE publishedPublication date reported by the CVE source.
- Jan 24, 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.
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