dbcve.org
MiuiOperating system · Mi

CVE-2020-14122

MEDIUM · 5.5 CVSS v3.1 Published 2022-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Some Xiaomi phones have information leakage vulnerabilities, and some of them may be able to forge a specific identity due to the lack of parameter verification, resulting in user information leakage.

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

Vulnerability in Xiaomi phone firmware stems from missing parameter validation that allows identity forgery and unauthorized access to user information. Attackers can potentially exploit the lack of input verification to impersonate legitimate users and extract personal data.

MitigationApply vendor security patches from Xiaomi as they become available. Until then, limit exposure by avoiding untrusted networks and applications that request sensitive identity information.

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:= 12.5.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Check installed Miui version
    On the Xiaomi phone, go to Settings > About phone > MIUI version (or Settings > About phone > All specs > MIUI version). Note the version number displayed.
    Affected if The displayed version is exactly 12.5.2
  2. Confirm firmware version matches
    In the same About phone section, also verify the Android version and build number for completeness, though the primary check is the Miui version number.
    Affected if Miui version shows 12.5.2 exactly (not 12.5.1, 12.5.3, or other versions)
  3. Verify no custom ROM or modified firmware
    Check if the device is running stock Xiaomi Miui firmware (Settings > About phone > MIUI version should show official Xiaomi branding, not custom ROM names like LineageOS, PixelExperience, etc.)
    Affected if The device runs stock Miui 12.5.2 from Xiaomi (custom ROMs have different vulnerability profiles)

A user is affected if their Xiaomi phone runs exactly Miui version 12.5.2 with stock firmware, as this specific version lacks the parameter validation that prevents identity forgery and unauthorized access to user information.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor security patches from Xiaomi as they become available. Until then, limit exposure by avoiding untrusted networks and applications that request sensitive identity information.

Fix this in Miui Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14122 — 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-14122 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