dbcve.org
Pad 4 FirmwareOperating system · Mi

CVE-2019-15469

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 Pad 4 Android device with a build fingerprint of Xiaomi/clover/clover:8.1.0/OPM1.171019.019/V9.6.26.0.ODJCNFD: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 · high confidence

The Xiaomi Mi Pad 4 contains a pre-installed app (com.qualcomm.qti.callenhancement) with an exported component that permits microphone audio recording without proper access controls. This component can be invoked by any pre-installed app holding signatureOrSystem permissions, enabling unauthorized call recording to external storage.

MitigationSince this is a pre-installed OEM app, organizations should apply vendor firmware updates when available, or implement Mobile Device Management (MDM) policies to restrict app permissions and block unauthorized microphone access.

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
Pad 4 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. Identify the device model
    Check the device model number in Settings > About Phone > Model Number, or run: getprop ro.product.model
    Affected if The device is not a Xiaomi Mi Pad 4 (the affected product)
  2. Verify the vulnerable app is installed
    Check if the package com.qualcomm.qti.callenhancement exists by running: pm list packages | grep callenhancement, or use an app inspector to list installed packages
    Affected if The package com.qualcomm.qti.callenhancement is not present on the device (not vulnerable if absent)
  3. Inspect the app's exported component
    Decompile the APK (typically at /system/app/CallEnhancement/CallEnhancement.apk or /data/app/...) and examine AndroidManifest.xml for an exported activity, service, or receiver that handles audio recording
    Affected if An exported component with recording capability is declared in the manifest and android:exported=true is set
  4. Check app permissions granted
    Run: dumpsys package com.qualcomm.qti.callenhancement to view the requested and granted permissions, particularly INTERNET, RECORD_AUDIO, and WRITE_EXTERNAL_STORAGE
    Affected if The app holds RECORD_AUDIO permission and the component is exported to other signatureOrSystem apps
  5. Verify third-party app access potential
    List all pre-installed apps with signatureOrSystem permissions using: pm list packages -s --permissions | grep -i signatureOrSystem. Any such app could potentially invoke the vulnerable exported component
    Affected if Other pre-installed apps hold signatureOrSystem permissions that would allow them to invoke the exported component

If the device is a Xiaomi Mi Pad 4 and the com.qualcomm.qti.callenhancement app is present with an exported component accessible to signatureOrSystem apps, the device is affected by this vulnerability.

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

Since this is a pre-installed OEM app, organizations should apply vendor firmware updates when available, or implement Mobile Device Management (MDM) policies to restrict app permissions and block unauthorized microphone access.

Fix this in Pad 4 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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