dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-10608

MEDIUM · 5.5 CVSS v3.1 Published 2020-04-16
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
Information disclosure issue occurs as there is no binding between the secure keypad session and the secure display session that allows user to take control of the REE to stop the secure keypad session and read the keypad input. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, MSM8905, MSM8909

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

This CVE describes a missing session binding between the secure keypad and secure display in Qualcomm Snapdragon Trusted Execution Environment (TEE). The lack of binding allows an attacker with REE (Rich Execution Environment) control to terminate the secure keypad session and intercept keypad inputs, enabling information disclosure of what should be protected keystroke data.

MitigationThis is a firmware-level vulnerability requiring a patch from Qualcomm. Device manufacturers must obtain and integrate the updated secure world (TEE) firmware that implements proper session binding between secure input and display components.

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
Apq8009 FirmwareOperating system
Affected:all versions
Msm8905 FirmwareOperating system
Affected:all versions
Msm8909 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 Qualcomm chipset model
    Check the device specifications or use commands like 'cat /proc/cpuinfo' or 'getprop ro.hardware' on Android to identify the SoC. Look for Apq8009, Msm8905, or Msm8909.
    Affected if The device uses one of the affected chipset models (Apq8009, Msm8905, or Msm8909)
  2. Confirm TEE presence
    Check if the device has a Trusted Execution Environment by examining /proc/tee or using 'dmesg | grep -i tee' to look for TEE initialization messages.
    Affected if The device implements a TEE and the secure keypad feature relies on it
  3. Verify secure keypad feature is enabled
    Check if secure keypad or secure input functionality is in use. On Android, examine system logs or TEE debug interfaces for secure keypad session establishment. Look for references to 'secure keypad', 'keypad', or 'secure input' in TEE-related logs.
    Affected if Secure keypad or secure input feature is actively used on the device
  4. Check TEE firmware version
    Access TEE debug interfaces or firmware version information if available. This may require manufacturer tools or access to /dev/tee or /sys/firmware/tee. Consult vendor documentation for TEE version retrieval methods.
    Affected if TEE firmware version cannot be verified as patched or the device lacks TEE firmware update capability

A device is affected if it uses an Apq8009, Msm8905, or Msm8909 chipset with an active TEE that implements secure keypad functionality, and the TEE firmware has not been updated to include the session binding fix.

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 firmware-level vulnerability requiring a patch from Qualcomm. Device manufacturers must obtain and integrate the updated secure world (TEE) firmware that implements proper session binding between secure input and display components.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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