dbcve.org
Msm8905 FirmwareOperating system · Qualcomm

CVE-2019-2317

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
The secret key used to make the Initial Sequence Number in the TCP SYN packet could be brute forced and therefore can be predicted in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, Nicobar, QCM2150, QM215, SC8180X, SDM429, SDM439, SDM450, SDM632, SDX24, SDX55, SM6150, SM7150, SM8150

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 · moderate confidence

The secret key used to generate Initial Sequence Numbers (ISN) in TCP SYN packets on affected Snapdragon chipsets can be brute forced, allowing attackers to predict ISN values. This enables TCP sequence number prediction attacks, potentially leading to session hijacking or Man-in-the-Middle attacks.

MitigationApply vendor-supplied firmware/security patches from Qualcomm and device manufacturers. Users should ensure devices run the latest firmware version containing the fix.

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
Msm8905 FirmwareOperating system
Affected:all versions
Msm8909 FirmwareOperating system
Affected:all versions
Msm8917 FirmwareOperating system
Affected:all versions
Msm8920 FirmwareOperating system
Affected:all versions
Msm8937 FirmwareOperating system
Affected:all versions
Msm8940 FirmwareOperating system
Affected:all versions
Msm8953 FirmwareOperating system
Affected:all versions
Nicobar 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, run 'getprop ro.product.board' or check /proc/cpuinfo for the processor identifier. Alternatively, use a system info app to identify the Snapdragon model number.
    Affected if The chipset model matches any of: Msm8905, Msm8909, Msm8917, Msm8920, Msm8937, Msm8940, Msm8953, or Nicobar.
  2. Check the baseband firmware version
    On Android, run 'getprop gsm.version.baseband' or check Settings > About Phone > Baseband version. This displays the Qualcomm modem firmware version.
    Affected if The baseband version is from an unpatched release. All firmware versions listed for the affected chipsets are vulnerable.
  3. Verify device OEM and security patch level
    Check Settings > About Phone > Security patch level. Also note the device manufacturer and model to cross-reference with Qualcomm's advisory.
    Affected if The security patch level is earlier than the vendor-supplied fix date for CVE-2019-2317.
  4. Confirm the vulnerability applies to the network stack
    This flaw is in the baseband/modem firmware that handles TCP SYN packet generation. The vulnerability is present when the device's cellular or Wi-Fi driver uses the affected chipset's firmware for TCP sequence number generation.
    Affected if The device uses one of the affected Snapdragon chipsets with unpatched baseband firmware for TCP ISN generation.

A user is affected if their device contains a Qualcomm Snapdragon chipset from the affected list (Msm8905, Msm8909, Msm8917, Msm8920, Msm8937, Msm8940, Msm8953, Nicobar) and the baseband firmware has not been updated with the security patch for CVE-2019-2317.

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/security patches from Qualcomm and device manufacturers. Users should ensure devices run the latest firmware version containing the fix.

Fix this in Msm8905 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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