CVE-2019-13322
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 · uneditedThis vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Xiaomi Browser Prior to 10.4.0. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of the miui.share application. The issue results from the lack of proper validation of user-supplied data, which can result in an arbitrary application download. An attacker can leverage this vulnerability to execute code in the context of the user. Was ZDI-CAN-7483.
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 · high confidenceThe vulnerability in Xiaomi Browser prior to 10.4.0 stems from improper validation of user-supplied data within the miui.share application handler. This allows an attacker to trigger arbitrary application downloads by tricking users into visiting malicious web pages. The downloaded applications execute in the user's context, enabling arbitrary code execution.
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< 10.4.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify Xiaomi Browser installationCheck if the Xiaomi Browser app is present on the device. On Android, this can be done by querying installed packages using 'adb shell pm list packages' or checking the app drawer for 'Mi Browser' or 'Xiaomi Browser'. The package name is typically com.mi.android.brower or com.miui.browser.Affected if Xiaomi Browser is installed on the device
-
Retrieve installed browser versionObtain the version number of the installed Xiaomi Browser. On Android, use 'adb shell dumpsys package com.mi.android.brower' or check the app info in Settings > Apps > Mi Browser. Look for the Version or Version Name field.Affected if The version displayed is less than 10.4.0 (for example, 10.3.x, 10.2.x, or any version number below 10.4.0)
-
Verify miui.share handler presenceCheck if the miui.share application handler component exists on the system. This can be examined by reviewing the AndroidManifest.xml of the browser app or by using 'adb shell pm dump com.mi.android.brower | grep -i share' to list components related to sharing.Affected if The miui.share handler is present and accessible within the Xiaomi Browser package
A user is affected if Xiaomi Browser is installed with a version number lower than 10.4.0, as this version range contains the vulnerable miui.share handler that allows arbitrary application downloads and code execution.
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 data10.4.0
Update Xiaomi Browser to version 10.4.0 or later. Additionally, implement proper validation of application download sources and user confirmation prompts before downloading or installing any applications.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13322 — 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-2019-13322 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