Local information disclosure via missing bounds check
Published Jan 4, 2022 · Updated Aug 3, 2024
Information disclosure in MediaTek libvcodecdrv on Android 11.0 allows local users to obtain sensitive information from the component. MediaTek has not identified the affected function or input path; it states only that libvcodecdrv accesses data without a required bounds check. Exploitation requires local access but no additional execution privileges or user interaction; the documented impact is disclosure only.
Summary
What happened
Information disclosure in MediaTek libvcodecdrv on Android 11.0 allows local users to obtain sensitive information from the component. MediaTek has not identified the affected function or input path; it states only that libvcodecdrv accesses data without a required bounds check. Exploitation requires local access but no additional execution privileges or user interaction; the documented impact is disclosure only.
The record
- CVE
- CVE-2022-20020
- Published
- Jan 4, 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
- Jan 4, 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