dbcve.org
Mdm9150 FirmwareOperating system · Qualcomm

CVE-2019-14008

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 null pointer dereference issue in location assistance data processing due to missing null check on resources before using it in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in MDM9150, MDM9607, MDM9650, SDM660, SDM845, SM8150, SM8250, 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 location assistance data processing code of Qualcomm Snapdragon chipsets. The code fails to validate that required resources are non-null before accessing them, potentially causing a denial of service or enabling arbitrary code execution when specially crafted location assistance data is processed.

MitigationApply the Qualcomm firmware patch (expected via OEM/carrier OTA updates) and verify that location assistance functionality operates normally after the update.

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
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Sdm660 FirmwareOperating system
Affected:all versions
Sdm845 FirmwareOperating system
Affected:all versions
Sm8150 FirmwareOperating system
Affected:all versions
Sm8250 FirmwareOperating system
Affected:all versions
Sxr2130 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Check system information via /proc/cpuinfo, android.settings, or baseband information (dumpsys iphonesubinfo or at Commands). Look for chipset identifiers such as Mdm9150, Mdm9607, Mdm9650, Sdm660, Sdm845, Sm8150, Sm8250, or Sxr2130.
    Affected if The device uses any of the affected chipset models listed in the CVE (Mdm9150, Mdm9607, Mdm9650, Sdm660, Sdm845, Sm8150, Sm8250, or Sxr2130).
  2. Determine the firmware version
    Retrieve the baseband or radio firmware version using AT commands (at+ver), or via android system properties (getprop gsm.version.baseband, getprop ro.build.version.firmware). Compare the firmware version against the affected ranges.
    Affected if The installed firmware version matches the affected products (all versions of the listed chipsets).
  3. Verify location assistance feature is present
    Check if location assistance data processing functionality is available on the device. This may be indicated by location-related services, GPS support, or assisted GPS (A-GPS) modules. Inspect system logs or location provider configurations.
    Affected if Location assistance functionality is present and the device processes location assistance data (required for the vulnerability to be exploitable).
  4. Check baseband/patch level
    Examine the baseband processor version string or patch level information (often accessible via *#*#4636#*#* on Android, or through engineering mode menus). Compare against known vulnerable firmware builds.
    Affected if The baseband patch level is unpatched or predates the CVE-2019-14008 fix release date.

A device is affected if it runs any of the listed Qualcomm chipsets (Mdm9150, Mdm9607, Mdm9650, Sdm660, Sdm845, Sm8150, Sm8250, or Sxr2130) with unpatched firmware and has location assistance 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 the Qualcomm firmware patch (expected via OEM/carrier OTA updates) and verify that location assistance functionality operates normally after the update.

Fix this in Mdm9150 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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