Local information disclosure via exposed AEE property
Published Feb 5, 2021 · Updated Aug 4, 2024
Information disclosure in MTK-based OPPO Android phones on Android 8.1 through 11 allows local users to read an AEE enforcement property. The Android property interface exposes ro.vendor.aee.enforcing through adb shell getprop, which returns the vendor AEE enforcement state as no. Low-privilege local access through an ADB shell is required, and the reported consequence is limited to disclosure of that security-enforcement state.
Summary
What happened
Information disclosure in MTK-based OPPO Android phones on Android 8.1 through 11 allows local users to read an AEE enforcement property. The Android property interface exposes ro.vendor.aee.enforcing through adb shell getprop, which returns the vendor AEE enforcement state as no. Low-privilege local access through an ADB shell is required, and the reported consequence is limited to disclosure of that security-enforcement state.
The record
- CVE
- CVE-2020-11836
- Published
- Feb 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1426
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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