dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-2271

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-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
Buffer over read can happen while parsing downlink session management OTA messages if network sends un-intended values in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, MDM9150, MDM9205, MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8939, MSM8940, MSM8953, MSM8976, MSM8996AU, MSM8998, Nicobar, QCM2150, QCS605, QM215, SC8180X, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, Snapdragon_High_Med_2016, 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 buffer over-read vulnerability exists in the downlink session management OTA message parsing code on Qualcomm Snapdragon chipsets. When the modem receives network-sent OTA messages with un-intended/malformed values, the parsing logic reads beyond the allocated buffer boundaries, potentially exposing sensitive memory contents. This critical flaw is remotely exploitable over the network without authentication.

MitigationApply vendor-supplied firmware patches from Qualcomm through device OEM updates. Organizations should inventory affected devices and monitor for available security updates from device manufacturers.

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
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Mdm915 FirmwareOperating system
Affected:all versions
Mdm9205 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 device chipset model
    Retrieve the device's Qualcomm modem/baseband chipset model. On Android, check Settings > About Phone > Baseband, or use terminal commands like 'cat /proc/cpuinfo' or 'getprop ro.baseband'. For IoT/embedded devices, consult the hardware specifications or FCC documentation.
    Affected if The chipset model matches Apq8009, Apq8017, Apq8053, Apq8096au, Apq8098, Mdm915, Mdm9205, or Mdm9206.
  2. Confirm modem firmware source
    Verify that the device uses Qualcomm's modem firmware for downlink session management OTA message parsing. This is inherent to the listed chipset families.
    Affected if The device incorporates one of the affected Qualcomm chipset models.
  3. Check for available firmware updates
    Contact the device OEM or check the manufacturer support website for any available security firmware updates addressing this CVE.
    Affected if No vendor patch has been applied to address CVE-2019-2271.

If the device contains any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8096au, Apq8098, Mdm915, Mdm9205, Mdm9206) and lacks the corresponding vendor firmware patch, the environment is affected by this 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches from Qualcomm through device OEM updates. Organizations should inventory affected devices and monitor for available security updates from device manufacturers.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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