dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-10587

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-05
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
Possible Stack overflow can occur when processing a large SDP body or non standard SDP body without right delimiters in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096, APQ8096AU, APQ8098, MDM9150, MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCM2150, QCS605, QM215, Rennell, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130

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

Stack overflow vulnerability in SDP (Session Description Protocol) parsing within multiple Qualcomm Snapdragon chipsets. The overflow occurs due to insufficient bounds checking when processing abnormally large SDP bodies or malformed SDP bodies lacking proper delimiters, potentially allowing arbitrary code execution or denial of service.

MitigationApply vendor-provided firmware/microcode updates from Qualcomm and device OEMs. Until patches are available, avoid processing untrusted SDP content from untrusted sources and disable unnecessary SDP-handling services.

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
Mdm9206 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 chipset model
    On Android devices, check /proc/cpuinfo or use 'getprop ro.board.platform'. On Linux embedded systems, check /proc/cpuinfo or dmidecode. On iOS, this may require jailbreak or checking device specifications.
    Affected if The chipset model is one of: Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Mdm9150, Mdm9206
  2. Verify firmware version
    Check the firmware/baseband version via 'getprop ro.build.version.all_codenames' on Android, or check modem firmware version through manufacturer tools or device diagnostics.
    Affected if Any firmware version on the affected chipsets is vulnerable (all versions are affected)
  3. Check if SDP services are running
    Look for processes or services handling SDP or media sessions. On Android, check running processes for SDP-related services, or examine logcat for SDP parsing activity. Check /system/etc or /vendor/etc for SDP configuration files.
    Affected if SDP-handling services or processes are active on the device
  4. Verify SDP parsing is enabled
    Check device configuration for SDP profile support in telephony or VoIP settings. Examine configuration files in /etc or /vendor/etc that control SDP processing. Look for SDP-enabled applications or services.
    Affected if SDP parsing or SDP-handling functionality is enabled in the device configuration

A defender is affected if the device uses one of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8096, Apq8096au, Apq8098, Mdm9150, Mdm9206) and has SDP parsing functionality enabled.

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-provided firmware/microcode updates from Qualcomm and device OEMs. Until patches are available, avoid processing untrusted SDP content from untrusted sources and disable unnecessary SDP-handling services.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation60.0 h
  • Testing32.0 h
  • Review / QA16.0 h
120.0 hours of engineering $20,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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