CVE-2022-20101
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn aee daemon, there is a possible information disclosure due to a path traversal. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06419017; Issue ID: ALPS06270870.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in the aee daemon allows local attackers to read arbitrary files on the system by manipulating file paths to escape the intended directory boundaries, leading to local information disclosure without requiring elevated privileges or user interaction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 11.0= 12.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Android versionNavigate to Settings > About Phone > Android version (or use 'getprop ro.build.version.release' via ADB shell)Affected if The reported version is 11.0 or 12.0 exactly
-
Locate aee daemonCheck if the aee daemon exists on the device by searching for 'aee' in /system/bin or /vendor/bin (or use 'find / -name '*aee*' 2>/dev/null' via ADB shell with root)Affected if The aee daemon binary is present on the device
-
Verify daemon is runningRun 'ps -A | grep aee' or 'ps -ef | grep aee' via ADB shell to check if the aee daemon process is actively runningAffected if The aee daemon process is currently executing
-
Check for unauthorized file access logsReview logcat output or system logs (particularly /data/log/ or /data/dumpstate/) for unusual file read operations referencing the aee daemon (look for 'open' or 'read' syscalls with suspicious paths like ../../)Affected if Logs show the aee daemon accessing files outside its intended directory (path traversal patterns)
The device is affected if it runs Android version 11.0 or 12.0 and contains the aee daemon, which could allow a local attacker to read arbitrary files via path traversal.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply vendor patch ALPS06419017 to address the path traversal vulnerability in the aee daemon; if immediate patching is not feasible, restrict physical and local access to affected devices and monitor for suspicious file access patterns.
- Check the Android Security Patch Level on the device to confirm if the May 2022 or later security patch is installed
- If the device is on Android 11.0 or 12.0 with MediaTek chipset, contact the device manufacturer or MediaTek for the specific patch (ALPS06419017)
- Apply the vendor-supplied security update that includes the fix for ALPS06419017
- Verify the patch has been applied by checking the Android Security Patch Level in Settings > About Phone > Android version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20101 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data