CVE-2019-14022Network attack vector

Denial of service via unchecked IPv6 header length

Published Apr 16, 2020 · Updated Aug 5, 2024

Reachable assertion in Qualcomm Snapdragon firmware across listed chipsets allows remote attackers to cause a service interrupt via malformed IPv6 headers. The IPv6 header extraction routine accepts an invalid length without checking the field before processing, triggering an assertion failure in modem data handling. Exploitation requires delivery of a crafted IPv6 packet to an exposed Snapdragon networking path and results in denial of service; confidentiality and integrity impact are not reported.

CVSS severity7.5
High
EPSS probability0.81%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Reachable assertion in Qualcomm Snapdragon firmware across listed chipsets allows remote attackers to cause a service interrupt via malformed IPv6 headers. The IPv6 header extraction routine accepts an invalid length without checking the field before processing, triggering an assertion failure in modem data handling. Exploitation requires delivery of a crafted IPv6 packet to an exposed Snapdragon networking path and results in denial of service; confidentiality and integrity impact are not reported.

The record

CVE
CVE-2019-14022
Published
Apr 16, 2020
Updated
Aug 5, 2024
Vendor
Qualcomm
Product
Snapdragon
Classifications
CWE-617, T1499
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 16, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=APQ8096AU, MDM9205, MDM9206, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, Nicobar, QCM2150, QCS605, QM215, Rennell, SC7180, SC8180X, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Qualcomm · Snapdragonversion=APQ8096AU, MDM9205, MDM9206, MDM9607, MDM9640, MDM9650, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, Nicobar, QCM2150, QCS605, QM215, Rennell, SC7180, SC8180X, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SDX55, SM6150, SM7150, SM8150, SXR1130

Published CVSS scores

7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
7.8NIST NVDAV:N/AC:L/Au:N/C:N/I:N/A:C

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-617Reachable Assertion
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo