dbcve.org
Mix 2s FirmwareOperating system · Mi

CVE-2019-15471

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 Mix 2S Android device with a build fingerprint of Xiaomi/polaris/polaris:8.0.0/OPR1.170623.032/V9.5.19.0.ODGMIFA:user/release-keys contains a pre-installed app with a package name of com.qualcomm.qti.callenhancement app (versionCode=27, versionName=8.1.0) that allows other pre-installed apps to perform microphone audio recording via an accessible app component. This capability can be accessed by any pre-installed app on the device which can obtain signatureOrSystem permissions that are required by other other pre-installed apps that export their capabilities to other pre-installed app. This app allows a third-party app to use its open interface to record telephone calls to external storage.

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

The com.qualcomm.qti.callenhancement pre-installed app on Xiaomi Mi Mix 2S (Android 8.0.0) exposes an accessible component that allows other pre-installed apps holding signatureOrSystem permissions to perform microphone audio recording. This enables unauthorized telephone call recording to external storage without user consent.

MitigationDevice firmware update from Xiaomi/Qualcomm to patch or remove the vulnerable callenhancement app; alternatively, enterprises may implement MDM policies to block microphone access for this app or consider device replacement if updates unavailable.

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
Mix 2s 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
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. Verify device model is Xiaomi Mi Mix 2S
    Check the device model number in Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shell
    Affected if Device model is NOT Xiaomi Mi Mix 2S - the vulnerability only affects this specific model
  2. Confirm com.qualcomm.qti.callenhancement app is installed
    List installed packages via 'pm list packages | grep callenhancement' in ADB shell, or check in Settings > Apps > Show system apps for 'Call Enhancement'
    Affected if The app is present - the vulnerable component exists only when this app is installed
  3. Check for other pre-installed apps with signatureOrSystem permissions
    Use 'dumpsys package <package_name> | grep -i permission' to inspect permissions of pre-installed apps, looking for signatureOrSystem or signature|system privileges
    Affected if Multiple pre-installed apps hold signatureOrSystem permissions - any such app could exploit the vulnerable component to access the microphone
  4. Verify Android OS version
    Check Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Device runs Android 8.0.0 on Mi Mix 2S - the vulnerability was discovered on this version but affects all firmware versions

User is affected if they use a Xiaomi Mi Mix 2S device with the com.qualcomm.qti.callenhancement app present and have other pre-installed apps with signatureOrSystem permissions that could access the exposed recording component.

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

Device firmware update from Xiaomi/Qualcomm to patch or remove the vulnerable callenhancement app; alternatively, enterprises may implement MDM policies to block microphone access for this app or consider device replacement if updates unavailable.

Fix this in Mix 2s Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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