Local information disclosure via incorrect bounds check
Published Feb 9, 2022 · Updated Aug 3, 2024
Information disclosure in MediaTek's ion driver on Android 10.0 and 11.0 allows local users to read sensitive information. The ion driver's incorrect bounds check fails to confine a local request to its intended data boundary. Exploitation requires low-privileged local access, needs no user interaction, and affects only devices using the listed MediaTek chipsets.
Summary
What happened
Information disclosure in MediaTek's ion driver on Android 10.0 and 11.0 allows local users to read sensitive information. The ion driver's incorrect bounds check fails to confine a local request to its intended data boundary. Exploitation requires low-privileged local access, needs no user interaction, and affects only devices using the listed MediaTek chipsets.
The record
- CVE
- CVE-2022-20036
- Published
- Feb 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, CWE-200
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 9, 2022CVE 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