CVE-2020-14118
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 · uneditedAn intent redirection vulnerability in the Mi App Store product. This vulnerability is caused by the Mi App Store does not verify the validity of the incoming data, can cause the app store to automatically download and install apps.
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 confidenceIntent redirection vulnerability in Mi App Store where the app fails to validate incoming intent data, allowing unauthenticated actors to trigger automatic downloads and installations of arbitrary applications through the vulnerable app store application.
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< 4.10.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Mi App Store installed versionUse Android PackageManager to query the package version: 'adb shell dumpsys package com.xiaomi.mitunes' or check via Settings > Apps > Mi App Store > Version info. Compare the version code/name against the affected range (< 4.10.0).Affected if The installed version is any version prior to 4.10.0 (e.g., 4.9.x, 4.8.x, etc.).
-
Confirm Mi App Store package nameVerify the exact package name of the installed app store on the device. Common package names include com.xiaomi.mitunes, com.xiaomi.shop, or com.miui.mistore. Use 'adb shell pm list packages | grep -i mi' to list Xiaomi packages.Affected if The installed package matches one of the known Mi App Store package names and version is below 4.10.0.
-
Verify the app handles download/install intentsSince this is an intent redirection vulnerability, the app must be configured to handle incoming intents for downloads or installations. Check if the app has intent-filter declarations for ACTION_VIEW or ACTION_INSTALL_PACKAGE by decompiling the APK and inspecting AndroidManifest.xml.Affected if The app declares intent filters for handling installation or download requests and the version is below 4.10.0.
You are affected if Mi App Store version is below 4.10.0 AND the app is installed and able to process external intents for app installations.
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 · scoped4.10.0
Implement strict validation and verification of all incoming intent data before processing download or installation requests, including origin verification and data integrity checks.
Mi App Store 4.10.0 or later
- Open the Mi App Store application
- Navigate to the app settings or profile section
- Check the current version of Mi App Store
- Update Mi App Store to version 4.10.0 or later through the in-app update mechanism or system app store
- Verify the update was successful by confirming the version number is 4.10.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14118 — 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-14118 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