Local information disclosure via APE heap over-read
Published Oct 25, 2021 · Updated Aug 3, 2024
An out-of-bounds read in the APE extractor on MediaTek chipsets running Android 10.0 and 11.0 allows local users to disclose memory. A heap-buffer overflow causes the extractor to read beyond the allocated buffer; MediaTek has not published the faulty function or triggering field. A local user needs no additional execution privileges or user interaction, and the reported consequence is limited to information disclosure.
Summary
What happened
An out-of-bounds read in the APE extractor on MediaTek chipsets running Android 10.0 and 11.0 allows local users to disclose memory. A heap-buffer overflow causes the extractor to read beyond the allocated buffer; MediaTek has not published the faulty function or triggering field. A local user needs no additional execution privileges or user interaction, and the reported consequence is limited to information disclosure.
The record
- CVE
- CVE-2021-0616
- Published
- Oct 25, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 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?
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