CVE-2020-14106
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 · uneditedThe application in the mobile phone can unauthorized access to the list of running processes in the mobile phone, Xiaomi Mobile Phone MIUI < 2021.01.26.
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 · moderate confidenceA vulnerability in Xiaomi MIUI mobile firmware prior to version 2021.01.26 allows any installed application to unauthorized access the list of running processes on the device. This enables malicious apps to enumerate running applications, potentially gathering intelligence about user activity or identifying security tools running on the device.
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< 2021.01.26CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Verify the device is running Xiaomi MIUI firmwareCheck the device's operating system information in Settings > About Phone. Look for MIUI branding and version identifier in the software information section.Affected if The device does not show MIUI as the firmware (for example, it runs stock Android or another custom ROM).
-
Locate the MIUI version numberNavigate to Settings > About Phone > MIUI Version. Record the full version string displayed (for example, V12.0.10.0.QJGEUXM).Affected if The MIUI version field is missing or unavailable, indicating non-MIUI firmware.
-
Compare your MIUI version against the vulnerable rangeExamine the version date embedded in the MIUI version string. The format typically includes a date code (such as 20.x.x.x for 2020 builds). Compare this against the January 26, 2021 cutoff: versions built before 2021.01.26 are vulnerable.Affected if The MIUI version date code is earlier than 2021.01.26 (for example, 20.12.10.0 or 20.8.15.0).
-
Confirm Android version as secondary indicatorIn Settings > About Phone > Android Version, note the Android OS version. This vulnerability affects MIUI specifically regardless of Android version, but recording this helps with full vulnerability context.Affected if This check is informational only; the vulnerability is determined by MIUI version, not Android version.
A Xiaomi device is affected if it runs MIUI firmware with a version date earlier than January 26, 2021.
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.
From vendor data2021.01.26
Update Xiaomi devices to MIUI version 2021.01.26 or later, which contains the patch to restrict unauthorized process enumeration. Users should verify their MIUI version in Settings > About Phone and apply system updates promptly.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14106 — 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-2020-14106 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