dbcve.org
Redmi Note 6 Pro FirmwareOperating system · Mi

CVE-2019-15470

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 Redmi Note 6 Pro Android device with a build fingerprint of xiaomi/tulip/tulip:8.1.0/OPM1.171019.011/V10.2.2.0.OEKMIXM: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

A pre-installed app (com.qualcomm.qti.callenhancement v8.1.0) on Xiaomi Redmi Note 6 Pro exposes an accessible component that allows other pre-installed apps with signatureOrSystem permissions to record microphone audio. This enables third-party apps to exploit the open interface to record telephone calls to external storage.

MitigationThis is a system-level vulnerability requiring OEM action. Users should avoid installing apps from untrusted sources and await an official device firmware update from Xiaomi. Enterprise mobility teams may consider MDM policies to restrict app permissions.

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
Redmi Note 6 Pro 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
    Check if the device is Xiaomi Redmi Note 6 Pro by going to Settings > About Phone > Model Number, or run: `getprop ro.product.model`
    Affected if Device model is NOT Xiaomi Redmi Note 6 Pro (this vulnerability only affects this specific model)
  2. Check for vulnerable app package
    Check if com.qualcomm.qti.callenhancement is installed by running: `pm list packages | grep callenhancement` or using a package manager app
    Affected if The package com.qualcomm.qti.callenhancement is present on the device
  3. Verify app version
    Check the app version using: `dumpsys package com.qualcomm.qti.callenhancement | grep versionName` or view in Settings > Apps > Call Enhancement
    Affected if Version is 8.1.0 or any version of this pre-installed app on Redmi Note 6 Pro
  4. Audit signatureOrSystem permission holders
    List apps holding signatureOrSystem permissions: `pm list packages -s | xargs pm dump_permissions | grep -B5 signatureOrSystem` or manually review app permissions in Settings > Apps > Permissions
    Affected if Any pre-installed app (not from Play Store) requests and abuses the signatureOrSystem permission level to access the exposed component
  5. Monitor for unauthorized audio recording
    Check for unexpected audio recording activity: Review running processes for audio recording apps, check file explorer for recently created .amr or .wav files in /storage/emulated/0/, or review app usage stats for microphone access
    Affected if Audio recordings appear on external storage without user-initiated call recording, or unknown apps show microphone permission activity

A user is affected if they have a Xiaomi Redmi Note 6 Pro with the com.qualcomm.qti.callenhancement pre-installed app that exposes its recording interface to other signatureOrSystem privileged apps.

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

This is a system-level vulnerability requiring OEM action. Users should avoid installing apps from untrusted sources and await an official device firmware update from Xiaomi. Enterprise mobility teams may consider MDM policies to restrict app permissions.

Fix this in Redmi Note 6 Pro Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Review / QA2.0 h
6.0 hours of engineering $1,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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