Local privilege escalation via secmem type confusion
Published Nov 6, 2023 · Updated Apr 29, 2025
Type confusion in MediaTek secmem on affected chipsets running Android 11.0 through 13.0 allows local users to escalate privileges. The secmem component performs an incorrect comparison that permits an incompatible-type access and corrupts memory. Successful exploitation requires existing System execution privileges but no user interaction; MediaTek has not disclosed the resulting privilege level.
Summary
What happened
Type confusion in MediaTek secmem on affected chipsets running Android 11.0 through 13.0 allows local users to escalate privileges. The secmem component performs an incorrect comparison that permits an incompatible-type access and corrupts memory. Successful exploitation requires existing System execution privileges but no user interaction; MediaTek has not disclosed the resulting privilege level.
The record
- CVE
- CVE-2023-32834
- Published
- Nov 6, 2023
- Updated
- Apr 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-843, CWE-697, T1404
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 6, 2023CVE publishedPublication date reported by the CVE source.
- Apr 29, 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