dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-10532

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Null-pointer dereference issue can occur while calculating string length when source string length is zero in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8064, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8996, Nicobar, QCS605, QM215, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, SM6150, 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 · high confidence

A null-pointer dereference vulnerability exists in the string length calculation function within Qualcomm Snapdragon chipsets. When the source string length is zero, the function attempts to dereference a null pointer, leading to potential memory corruption, denial of service, or possible arbitrary code execution.

MitigationApply vendor-supplied firmware patches from Qualcomm and subsequent device manufacturer updates. Identify all affected devices in the environment and prioritize patching based on exposure.

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
Apq8064 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9207c 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 or system
    On Android devices, use 'Settings > About Phone > Baseband' or run 'adb shell getprop ro.board.platform' and 'adb shell getprop ro.product.device'. On Linux embedded systems, check 'cat /proc/cpuinfo' or 'lspci' output. For network equipment, consult vendor documentation or SNMP MIBs.
    Affected if The chipset model matches any of: Apq8009, Apq8017, Apq8053, Apq8064, Apq8096au, Apq8098, Mdm9206, Mdm9207c
  2. Confirm the chipset is a Snapdragon variant from the affected product line
    Cross-reference the identified chipset model with Qualcomm's product naming. Apq-series are application processors, Mdm-series are modems. All listed models are part of the Snapdragon family.
    Affected if The chipset is definitively identified as one of the eight listed model numbers from the affected products list
  3. Determine if your device firmware can receive the vulnerable string processing input
    Identify whether the system exposes any interfaces (e.g., network services, USB functions, NFC, Bluetooth, or radio firmware) that process string data where an attacker-controlled zero-length string could reach the affected function. Review application and kernel logs for crashes or errors mentioning null-pointer dereferences in string handling code.
    Affected if The device has active input paths that could trigger the string length calculation function with a zero-length source string, or you observe related crash logs

If your environment contains any device using the Apq8009, Apq8017, Apq8053, Apq8064, Apq8096au, Apq8098, Mdm9206, or Mdm9207c Qualcomm chipset, you are affected since all firmware versions for these models contain the 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches from Qualcomm and subsequent device manufacturer updates. Identify all affected devices in the environment and prioritize patching based on exposure.

Recommended fix High confidence
  1. This is a firmware-level vulnerability in Qualcomm Snapdragon chipsets that cannot be remediated through end-user action.
  2. Contact your device manufacturer (OEM) to request firmware updates addressing CVE-2019-10532.
  3. Monitor Qualcomm's official security advisories (www.qualcomm.com) for downstream firmware releases from your OEM.
  4. Apply OEM-provided firmware updates once they become available for your specific device model.
Caveat Firmware updates must come from device OEMs; no direct user action possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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