CVE-2020-14114
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 · uneditedinformation leakage vulnerability exists in the Xiaomi SmartHome APP. This vulnerability is caused by illegal calls of some sensitive JS interfaces, which can be exploited by attackers to leak sensitive information.
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 vulnerability exists in the Xiaomi SmartHome APP where certain sensitive JavaScript interfaces can be called illegally, allowing attackers to bypass intended access controls and extract sensitive information from the application or connected devices.
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<= 6.4.701CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check installed Mi SmartHome app versionOpen the app store (Google Play Store or iOS App Store), search for 'Mi SmartHome' or 'Xiaomi SmartHome', and view the installed version. On Android, go to Settings > Apps > Mi SmartHome > Version. On iOS, go to Settings > General > iPhone Storage > Mi SmartHome to see the version.Affected if The installed version is 6.4.701 or any version number lower than 6.4.701 (e.g., 6.4.700, 6.4.600, 6.4.500, etc.)
-
Compare version against affected rangeTake the version number found in step 1 and compare it numerically to 6.4.701. Any version that is less than or equal to 6.4.701 is in the affected range.Affected if The version is <= 6.4.701, meaning the app has the vulnerable JavaScript interface exposure
-
Verify WebView JavaScript interface exposure (Android)If running on Android and you have access to the app's debug build or APK, analyze the WebView configuration for exposed JavaScript interfaces using tools like jadx to decompile the APK and inspect the WebView settings. Look for addJavascriptInterface() calls that expose sensitive methods to WebView content.Affected if The app uses addJavascriptInterface() with sensitive native methods exposed to JavaScript content without proper origin validation
-
Check for legacy interface communication patternsIf you can inspect network traffic from the app (using a proxy like Burp Suite or Charles), observe whether the app communicates with device hubs using WebSocket or HTTP endpoints that accept JavaScript bridge calls without consistent authentication tokens.Affected if The app uses unauthenticated or improperly validated JavaScript bridge calls to communicate with smart home devices
You are affected if the Mi SmartHome/Xiaomi SmartHome application installed on your device is version 6.4.701 or any earlier version, as these versions contain the vulnerable JavaScript interface exposure that allows unauthorized access to sensitive functions.
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 dataRestrict access to sensitive JS interfaces by implementing proper authentication, origin validation, and access control checks; update the application to use safe interface communication patterns.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14114 — 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-14114 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