dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-10482

MEDIUM · 5.9 CVSS v3.1 Published 2019-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Due to the use of non-time-constant comparison functions there is issue in timing side channels which can be used as a potential side channel for SUI corruption 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, APQ8017, APQ8053, APQ8096, APQ8096AU, APQ8098, MDM9150, MDM9205, MDM9206, MDM9607, MDM9650, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996, MSM8996AU, MSM8998, Nicobar, QCS404, QCS405, QCS605, QM215, SA6155P, SC8180X, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

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

Non-time-constant comparison functions in Snapdragon chipsets create timing side channels that could potentially be exploited to infer information and corrupt the Secure User Interface (SUI). An attacker with precision timing measurement capabilities could analyze execution time differences during comparison operations to leak sensitive data.

MitigationApply vendor firmware/security patches from Qualcomm. Until patches are available, minimize exposure by restricting physical access and reducing attack surface for timing measurement.

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
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9205 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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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 in your device
    On Android, check /proc/cpuinfo or go to Settings > About Phone > CPU info. Look for the processor identifier (e.g., Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Mdm9150, or Mdm9205).
    Affected if The chipset matches one of the following: Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Mdm9150, or Mdm9205.
  2. Check the firmware or baseband version
    On Android, go to Settings > About Phone > Baseband version or Settings > About Phone > Software Information > Build number. Note the firmware version string.
    Affected if Firmware version is present and the device uses one of the affected chipsets listed above.
  3. Check the Android security patch level
    On Android, go to Settings > About Phone > Security Patch Level. This indicates the date of the last security update.
    Affected if Security patch level is earlier than the vendor fix date for CVE-2019-10482, or the device has not received firmware updates from Qualcomm.
  4. Determine if Secure User Interface (SUI) is in use
    Check device documentation or system logs for references to Secure User Interface or SUI functionality. This feature handles sensitive UI operations on affected chipsets.
    Affected if The device utilizes the Secure User Interface (SUI) feature and runs on an affected chipset with unpatched firmware.

A device is affected if it contains any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Mdm9150, Mdm9205) with firmware that has not been updated to include the timing side-channel mitigation.

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

Apply vendor firmware/security patches from Qualcomm. Until patches are available, minimize exposure by restricting physical access and reducing attack surface for timing measurement.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
50.0 hours of engineering $8,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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