dbcve.org
Apq8096au FirmwareOperating system · Qualcomm

CVE-2019-14022

HIGH · 7.5 CVSS v3.1 Published 2020-04-16
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
Error occurs While extracting the ipv6_header having an invalid length due to lack of length check in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in 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

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 missing length check in IPv6 header parsing in Snapdragon chipsets allows malformed packets with invalid IPv6 header lengths to trigger errors. The lack of bounds validation before header extraction could lead to buffer over-read conditions or denial of service when processing specially crafted network packets.

MitigationApply chipset-level firmware patches provided by Qualcomm and distributed through device OEMs. This is a hardware/firmware vulnerability that cannot be fixed through software configuration alone; users must obtain and install vendor-provided security updates.

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
Apq8096au FirmwareOperating system
Affected:all versions
Mdm9205 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8905 FirmwareOperating system
Affected:all versions
Msm8909 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 chipset model
    Determine the Qualcomm Snapdragon chipset present in the device or system. This may be found in device specifications, /proc/cpuinfo on Android devices, or system documentation. Look for model numbers matching: Apq8096au, Mdm9205, Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8905, or Msm8909.
    Affected if The chipset model matches one of the affected products listed in the CVE (Apq8096au, Mdm9205, Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8905, or Msm8909).
  2. Determine the firmware version
    Retrieve the baseband/modem firmware version from the device. On Android, this can often be found in Settings > About Phone > Baseband version, or via AT commands (AT+CGMR) if accessible. Check vendor documentation for firmware version retrieval specific to the device.
    Affected if The firmware version is present and corresponds to the affected chipset, as all firmware versions of these chipsets are affected per the CVE statement.
  3. Verify IPv6 processing is enabled
    Check if the device or network stack processes IPv6 traffic. On Linux systems, examine /proc/sys/net/ipv6/conf/all/disable_ipv6 or use 'ip -6 addr show'. On network devices, check IPv6 configuration status. The vulnerability triggers when processing IPv6 packets.
    Affected if IPv6 is enabled and the device processes IPv6 network traffic, as the vulnerability exists in IPv6 header parsing logic.
  4. Confirm network exposure to untrusted IPv6 traffic
    Evaluate whether the device can receive IPv6 packets from untrusted sources. This includes checking firewall rules (ip6tables -L), network segmentation, and whether the device is directly exposed to external network traffic.
    Affected if The device can receive IPv6 packets from potentially malicious sources, as the flaw is triggered by malformed IPv6 packets.

A device is likely affected if it contains one of the listed Qualcomm chipsets (Apq8096au, Mdm9205, Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8905, Msm8909), processes IPv6 traffic, and can receive packets from untrusted sources.

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 chipset-level firmware patches provided by Qualcomm and distributed through device OEMs. This is a hardware/firmware vulnerability that cannot be fixed through software configuration alone; users must obtain and install vendor-provided security updates.

Fix this in Apq8096au Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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