dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2019-2289

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
Lack of integrity check allows MODEM to accept any NAS messages which can result into authentication bypass of NAS 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 vulnerability in Qualcomm Snapdragon baseband/MODEM processors allows acceptance of NAS (Non-Access Stratum) messages without integrity verification. This enables authentication bypass of the NAS security layer, potentially allowing attackers to inject arbitrary messages into the cellular communication channel and compromise the device's network authentication.

MitigationThis is a firmware-level vulnerability requiring a patch from Qualcomm to the baseband/MODEM processor. Device manufacturers must integrate the patch and distribute firmware updates to affected devices. Users should apply vendor-supplied updates promptly.

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 the device baseband/MODEM processor model
    Use device diagnostic tools (such as *#*#4636#*#* on Android, or manufacturer-provided modem info in Settings > About Phone > Modem Version) or check the device's technical specifications to determine the Qualcomm Snapdragon chipset used for cellular baseband communication.
    Affected if The processor model matches any of: Apq8009, Apq8017, Apq8053, Apq8096au, Apq8098, Mdm915, Mdm9205, or Mdm9206.
  2. Check the baseband firmware version
    Navigate to Settings > About Phone > Modem Version (or similar path depending on device) to retrieve the installed baseband/MODEM firmware version. On Android, you can also use the command 'getprop gsm.version.baseband' via ADB shell.
    Affected if Any firmware version is installed on the affected processor models listed above, since all versions are vulnerable per the CVE.
  3. Verify NAS integrity verification is disabled
    This requires access to baseband debug logs or network protocol analysis tools to inspect whether NAS (Non-Access Stratum) messages from the network are being integrity-verified. Contact the device manufacturer for diagnostic access or check if the device supports integrity verification status in developer options.
    Affected if The device accepts NAS messages without integrity verification, which can only be confirmed through baseband-level diagnostics or manufacturer disclosure.
  4. Confirm device is actively using cellular connectivity
    Verify the device has an active cellular connection (2G/3G/4G/5G) and is communicating with a mobile network, as the vulnerability exploits the NAS security layer during cellular communication.
    Affected if The device is connected to a cellular network and uses one of the affected Qualcomm baseband processors.

The device is affected if it contains any of the following Qualcomm Snapdragon baseband/MODEM processors: Apq8009, Apq8017, Apq8053, Apq8096au, Mdm915, Mdm9205, Mdm9206, or Apq8098, regardless of firmware version.

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

This is a firmware-level vulnerability requiring a patch from Qualcomm to the baseband/MODEM processor. Device manufacturers must integrate the patch and distribute firmware updates to affected devices. Users should apply vendor-supplied updates promptly.

Recommended fix Moderate confidence

Qualcomm modem firmware update (contact OEM for specific version)

  1. Contact your device OEM (Original Equipment Manufacturer) to obtain the firmware/modem update that addresses CVE-2019-2289
  2. Apply the OEM-provided firmware update through your device's system update mechanism
  3. Verify the modem firmware version has been updated to a version containing the integrity check fix
  4. For embedded/IoT devices using affected Qualcomm chipsets, contact the device vendor for firmware updates
Caveat Firmware updates may require device downtime; ensure backup before applying

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

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation24.0 h
  • Testing32.0 h
  • Review / QA12.0 h
84.0 hours of engineering $14,480
Get help mitigating

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 locally
dbcve dependency scanner

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