CVE-2020-14117
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 · uneditedA improper permission configuration vulnerability in Xiaomi Content Center APP. This vulnerability is caused by the lack of correct permission verification in the Xiaomi content center APP, and attackers can use this vulnerability to invoke the sensitive component functions of the Xiaomi content center APP.
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 confidenceThe Xiaomi Content Center APP lacks proper permission verification on its exported components, allowing unauthenticated attackers to invoke sensitive internal functions. This is a classic Android exported component vulnerability where sensitive activities, services, or broadcast receivers can be accessed without appropriate permission checks.
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.4.11CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Verify Mi Content Center is installedCheck device application list or use package manager command: `pm list packages | grep com.xiaomi.mcc`Affected if The package com.xiomi.mcc is found on the device
-
Check installed versionUse package manager: `dumpsys package com.xiomi.mcc` or check app info in device settings under Mi Content CenterAffected if Version code or version name is less than 4.4.11
-
Extract AndroidManifest.xmlUse APK extraction tool (e.g., apktool, jadx) to decompile the installed APK and retrieve AndroidManifest.xmlAffected if APK is available and can be decompiled for inspection
-
Identify exported componentsIn AndroidManifest.xml, search for components with `android:exported="true"` attribute - look for activity, service, and receiver tagsAffected if Any sensitive components (activities, services, receivers) are marked as exported without android:permission attribute
-
Check for permission gaps on exported componentsFor each exported component, verify if android:permission or android:exported is set to false; if exported=true with no permission, the vulnerability existsAffected if Exported components handling sensitive operations lack android:permission protection
User is affected if Mi Content Center version is below 4.4.11 AND the app has exported components without proper android:permission attributes protecting sensitive operations.
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.4.11
Implement Android permission checks (via android:permission attribute or programmatic permission verification) on all exported components that handle sensitive operations, and audit the manifest to ensure only necessary components are exported.
Content Center version 4.4.11 or later
- Open the Xiaomi Content Center APP on your device
- Navigate to the app settings or check for updates in your device's app store
- Update the Content Center APP to version 4.4.11 or later
- Verify the update was successful by checking the app version in the app settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14117 — 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-14117 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