Local information disclosure via improper daemon access control
Published May 3, 2022 · Updated Aug 3, 2024
Improper access control in MediaTek's aee daemon on Android 11.0 and 12.0 allows local users to read protected information. MediaTek identifies an access-control failure in the daemon but does not publish the affected function or the operation that exposes data. Exploitation requires local low-privileged access but no user interaction or additional execution privileges, and the reported consequence is limited to confidentiality.
Summary
What happened
Improper access control in MediaTek's aee daemon on Android 11.0 and 12.0 allows local users to read protected information. MediaTek identifies an access-control failure in the daemon but does not publish the affected function or the operation that exposes data. Exploitation requires local low-privileged access but no user interaction or additional execution privileges, and the reported consequence is limited to confidentiality.
The record
- CVE
- CVE-2022-20104
- Published
- May 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 3, 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.
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