dbcve.org
MiuiOperating system · Mi

CVE-2020-14103

MEDIUM · 5.5 CVSS v3.1 Published 2021-04-08
Fix available
A fix is available. Upgrade to 2020.01.15 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
The application in the mobile phone can read the SNO information of the device, Xiaomi 10 MIUI < 2020.01.15.

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 confidence

A vulnerability in MIUI versions prior to 2020.01.15 on Xiaomi 10 devices allows any installed application to read the device's SNO (Serial Number) information without proper authorization, exposing sensitive device identification data.

MitigationUpdate MIUI to version 2020.01.15 or later to restrict application access to device serial number information. Users should also review app permissions and avoid installing untrusted applications.

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
MiuiOperating system
Affected:< 2020.01.15

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check device model number
    Go to Settings > About phone > Model number (or All specs) and verify the device is Xiaomi 10 / Mi 10 series
    Affected if Device is a Xiaomi 10 or Mi 10 variant and MIUI version is below 2020.01.15
  2. Check MIUI version via Settings
    Navigate to Settings > About phone > MIUI version and note the displayed version string
    Affected if Version shown is earlier than 2020.01.15 (e.g., 20.x.x, 19.x.x)
  3. Check MIUI version via hidden test menu
    Open the dialer and enter *#*#64663#*#* to access the version info screen, or use ADB command: adb shell getprop ro.miui.ui.version.name
    Affected if The returned version is lower than the January 2020 update (2020.01.15)
  4. Verify serial number access is unrestricted
    Attempt to read the device serial number (SNO) via an app or ADB command: adb shell getprop ro.serialno - if any application can retrieve this without special permission, the vulnerability is present
    Affected if SNO is readable without elevated permissions and MIUI version is below 2020.01.15

The device is affected if it is a Xiaomi 10 running MIUI version lower than 2020.01.15 and any installed application can read the device serial number without authorization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2020.01.15 or later
Fixed in 2020.01.15
Interim mitigation

Update MIUI to version 2020.01.15 or later to restrict application access to device serial number information. Users should also review app permissions and avoid installing untrusted applications.

Fix this in Miui Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14103 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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