System privilege escalation via unchecked imgsys write
Published Aug 7, 2023 · Updated Oct 22, 2024
Out-of-bounds write in MediaTek imgsys on Android 12.0, Android 13.0, and IoT Yocto 4.0 allows local users to gain System privileges. The imgsys component performs a memory write without first checking that the destination bounds contain the requested operation. Exploitation requires existing high local privileges on an affected MediaTek chipset, needs no user interaction, and grants System execution.
Summary
What happened
Out-of-bounds write in MediaTek imgsys on Android 12.0, Android 13.0, and IoT Yocto 4.0 allows local users to gain System privileges. The imgsys component performs a memory write without first checking that the destination bounds contain the requested operation. Exploitation requires existing high local privileges on an affected MediaTek chipset, needs no user interaction, and grants System execution.
The record
- CVE
- CVE-2023-20805
- Published
- Aug 7, 2023
- Updated
- Oct 22, 2024
- Vendor
- Yocto Project
- Product
- Yocto Project
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 7, 2023CVE publishedPublication date reported by the CVE source.
- Oct 22, 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=4.0
What conditions does exploitation require?
What is affected?
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