dbcve.org
A2 Lite FirmwareOperating system · Mi

CVE-2019-15468

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-14
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
The Xiaomi Mi A2 Lite Android device with a build fingerprint of xiaomi/daisy/daisy_sprout:9/PKQ1.180917.001/V10.0.3.0.PDLMIXM:user/release-keys contains a pre-installed app with a package name of com.huaqin.factory app (versionCode=1, versionName=QL1715_201812071953) that allows unauthorized wireless settings modification via a confused deputy attack. This capability can be accessed by any app co-located on the device.

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 confidence

The Xiaomi Mi A2 Lite contains a pre-installed factory test app (com.huaqin.factory) that exposes privileged wireless settings modification capabilities without proper authorization checks. This confused deputy vulnerability allows any locally-installed application to manipulate wireless settings by leveraging the privileged position of the pre-installed app, requiring no authentication.

MitigationThe vendor should implement proper permission checks and authorization validation within the com.huaqin.factory app to prevent unauthorized access to wireless settings, or remove/disable the vulnerable pre-installed app from the device firmware.

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
A2 Lite FirmwareOperating system
Affected:all versions

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 device model
    Check if the device is a Xiaomi Mi A2 Lite by reviewing the device settings under Settings > About Phone > Model Number, or by running 'getprop ro.product.model' via ADB
    Affected if Device model is Mi A2 Lite - all firmware versions are affected
  2. Verify the vulnerable app is present
    Check if the package com.huaqin.factory is installed using 'pm list packages | grep huaqin' via ADB shell, or view installed packages in device settings
    Affected if The com.huaqin.factory package is found installed on the device
  3. Check if the app is exported and accessible
    Use 'dumpsys package com.huaqin.factory' via ADB to inspect the package flags, specifically looking for android:exported="true" in the manifest or exported components
    Affected if The app or its components are exported (android:exported=true) allowing other apps to interact with it
  4. Inspect app permissions
    Use 'dumpsys package com.huaqin.factory' to list the granted permissions, particularly focusing on system or privileged permissions related to Wi-Fi or network settings
    Affected if The app holds elevated permissions for wireless settings modification (e.g., CHANGE_WIFI_STATE, ACCESS_WIFI_STATE, or similar system-level permissions)
  5. Verify app is pre-installed system app
    Check the app's installation location using 'pm list packages -s | grep huaqin' or by examining the APK path via 'pm path com.huaqin.factory' in ADB shell
    Affected if The app is installed in /system/priv-app or /system/app indicating it is a pre-installed factory test application

If the device is a Xiaomi Mi A2 Lite with the com.huaqin.factory pre-installed system app present and exported, the device is vulnerable to local privilege escalation via this confused deputy flaw.

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

The vendor should implement proper permission checks and authorization validation within the com.huaqin.factory app to prevent unauthorized access to wireless settings, or remove/disable the vulnerable pre-installed app from the device firmware.

Fix this in A2 Lite Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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 locally
dbcve dependency scanner

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