CVE-2019-10589
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 · uneditedLack of length check of response buffer can lead to buffer over-flow while GP command response buffer handling in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8017, APQ8053, APQ8098, MDM9206, MDM9607, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8998, QM215, SDA660, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660
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 confidenceBuffer overflow vulnerability in GP command response buffer handling due to missing length validation. The flaw allows overflowing the response buffer when processing GP commands, potentially allowing arbitrary code execution or denial of service. Affected are numerous Qualcomm Snapdragon chipsets spanning mobile, IoT, compute, and infrastructure product lines.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the chipset modelCheck the device hardware or system information to determine the Qualcomm chipset in use. On Linux-based systems, this may be visible in /proc/cpuinfo, boot logs, or via AT commands such as 'AT+CGMM' or 'AT+GMM' on modem interfaces. Review hardware documentation or vendor specifications if available.Affected if The chipset matches one of the affected models: Apq8017, Apq8053, Apq8098, Mdm9206, Mdm9607, Msm8917, Msm8920, or Msm8937.
-
Determine the firmware versionQuery the firmware version through vendor-specific interfaces. On Qualcomm-based devices, this may be accessible via AT commands (for modems), through the /proc/version or /proc/bootinfo files, or via diagnostic tools provided by the device manufacturer. Compare the installed firmware version against any vendor-released patches or update notices.Affected if The firmware is an unpatched version and the chipset is on the affected list.
-
Verify if GP command interface is accessibleDetermine whether the GP command interface is exposed or enabled on the device. This may require access to diagnostic ports, debug interfaces, or modem AT command terminals. Check if the interface accepts external or untrusted inputs.Affected if The GP command interface is accessible and the device uses an affected chipset with unpatched firmware.
The device is affected if it uses any of the listed Qualcomm chipsets (Apq8017, Apq8053, Apq8098, Mdm9206, Mdm9607, Msm8917, Msm8920, Msm8937) and is running firmware that has not been updated with the vendor patch.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Qualcomm-provided firmware/patch updates to affected chipsets. Device manufacturers must integrate these patches and deliver via OTA updates to end-user devices. For unpatched devices, reduce attack surface by restricting untrusted inputs to GP command interfaces.
- Consultation16.0 h
- Implementation24.0 h
- Testing32.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $23,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10589 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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