dbcve.org
Mi BrowserApplication · Mi

CVE-2020-14116

HIGH · 7.5 CVSS v3.1 Published 2022-04-21
Fix available
A fix is available. Upgrade to 15.8.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An intent redirection vulnerability in the Mi Browser product. This vulnerability is caused by the Mi Browser does not verify the validity of the incoming data. Attackers can perform sensitive operations by exploiting this.

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

This is an intent redirection vulnerability in Xiaomi's Mi Browser where the application fails to validate incoming intents before processing them. Attackers can craft malicious intents to trigger sensitive operations or redirect data to unauthorized components, potentially exposing user data or performing actions on behalf of the user.

MitigationImplement strict validation of all incoming intents, verify the source of intents before acting on them, and use explicit intents with specific component names rather than implicit intents for sensitive operations.

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
Mi BrowserApplication
Affected:< 15.8.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify if Mi Browser is installed
    Check installed packages on the Android device: `pm list packages | grep miui.browser` or `pm list packages | grep xiaomi` to find browser-related packages
    Affected if No Mi Browser package found means this CVE does not apply
  2. Determine installed Mi Browser version
    Use `dumpsys package <package_name>` or check via Settings > Apps > Mi Browser to view the version number (e.g., 15.7.0, 15.8.0)
    Affected if Version is below 15.8.0 (e.g., 15.7.x, 15.6.x, earlier) indicates the device is in the affected version range
  3. Verify the app exports intent-receiving components
    Use `aapt dump badging <apk_path>` or `dumpsys package <package_name> | grep -i export` to list exported activities, receivers, and services that can accept intents from other apps
    Affected if Exported components exist and the version is below 15.8.0, meaning untrusted intents can reach the browser's internal components
  4. Confirm intent validation is absent
    Inspect the app's intent handling code or use dynamic analysis with intent fuzzing tools to observe whether incoming intents with arbitrary data are processed without source verification
    Affected if The browser accepts and acts on intents without validating the calling package or intent source, exposing the intent redirection attack surface

A device is affected if Mi Browser is installed with a version below 15.8.0 and the app exposes exported components that process unvalidated incoming intents.

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.

dbcve · scoped
Upgrade available Upgrade to 15.8.0 or later
Fixed in 15.8.0
Interim mitigation

Implement strict validation of all incoming intents, verify the source of intents before acting on them, and use explicit intents with specific component names rather than implicit intents for sensitive operations.

Recommended fix High confidence

Mi Browser version 15.8.0 or later

  1. Open the Mi Browser application on your Android device
  2. Navigate to the app settings or about section
  3. Check the current browser version under 'Version' or 'About Mi Browser'
  4. If version is below 15.8.0, access the Google Play Store
  5. Search for 'Mi Browser' or '小米浏览器'
  6. Update the application to the latest available version (15.8.0 or higher)
  7. Verify the update was successful by checking the version number again

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mi Browser Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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