dbcve.org
Ipq5018 FirmwareOperating system · Qualcomm

CVE-2020-3675

CRITICAL · 9.8 CVSS v3.1 Published 2020-09-08
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
u'Potential integer underflow while parsing Service Info and IPv6 link-local TLVs that comes as part of NDPE attribute' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ5018, IPQ6018, IPQ8074, Kamorta, Nicobar, QCA6390, QCN7605, QCS404, QCS405, Rennell, SA415M, Saipan, SC7180, SC8180X, SDX55, SM6150, SM7150, SM8150, SM8250

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

Integer underflow vulnerability in parsing Service Info and IPv6 link-local TLVs within NDPE (Neighbor Discovery Protocol Extension) attributes in Qualcomm Snapdragon chipset firmware. This memory corruption issue in IPv6 neighbor discovery processing could allow remote unauthenticated attackers to execute arbitrary code or cause denial of service.

MitigationApply vendor firmware updates from Qualcomm/OEMs for affected Snapdragon chips. Until patches are available, consider network segmentation to limit exposure of vulnerable IPv6 processing paths.

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
Ipq5018 FirmwareOperating system
Affected:all versions
Ipq6018 FirmwareOperating system
Affected:all versions
Ipq8074 FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions
Nicobar FirmwareOperating system
Affected:all versions
Qca6390 FirmwareOperating system
Affected:all versions
Qcn7605 FirmwareOperating system
Affected:all versions
Qcs404 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
    Check the device hardware specifications or use commands like 'lspci', 'cat /proc/cpuinfo', or check OEM documentation to confirm the exact Qualcomm Snapdragon chipset model (e.g., IPQ5018, QCA6390, etc.)
    Affected if The chipset matches one of the affected models: IPQ5018, IPQ6018, IPQ8074, Kamorta, Nicobar, QCA6390, QCN7605, or QCS404
  2. Check if IPv6 is enabled
    On the device, run 'sysctl net.ipv6.conf.all.disable_ipv6' or check network configuration files for IPv6 enablement status
    Affected if IPv6 is enabled (value returns 0), as the vulnerability exists in IPv6 neighbor discovery processing
  3. Verify NDPE service status
    Check if the Neighbor Discovery Protocol Extension (NDPE) service or module is running. This may appear in process lists ('ps' command), service configurations, or network service registrations
    Affected if NDPE/Neighbor Discovery processing is active and handling IPv6 link-local TLVs
  4. Check firmware version
    Query the firmware version through vendor-specific interfaces (bootloader, UEFI, modem AT commands, or OEM management portal). Compare against any vendor-released patch versions if available
    Affected if Firmware is an unpatched version from the affected product line (all versions of the listed chipsets are vulnerable)
  5. Inspect IPv6 NDPE TLV parsing
    If network traffic analysis is possible, capture and inspect IPv6 Neighbor Discovery packets being processed by the device for malformed Service Info or link-local TLV attributes
    Affected if The device processes IPv6 NDPE packets containing the vulnerable TLV structures

A user is affected if their device uses one of the listed Qualcomm Snapdragon chipsets with IPv6 and NDPE functionality enabled, running unpatched firmware.

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 firmware updates from Qualcomm/OEMs for affected Snapdragon chips. Until patches are available, consider network segmentation to limit exposure of vulnerable IPv6 processing paths.

Fix this in Ipq5018 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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