CVE-2020-3669
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 · uneditedu'Buffer Overflow issue in WLAN tcp ip verification due to usage of out of range pointer offset' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8098, IPQ5018, IPQ6018, IPQ8074, Kamorta, MSM8998, Nicobar, QCA6390, QCA8081, QCN7605, QCS404, QCS405, QCS605, Rennell, SA415M, SC7180, SC8180X, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SM6150, SM7150, SM8150, SM8250, 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 · moderate confidenceA buffer overflow vulnerability exists in the WLAN TCP/IP verification component of multiple Snapdragon chipsets. The issue stems from the use of an out-of-range pointer offset during verification operations, which can lead to memory corruption. This memory corruption could potentially allow remote attackers to execute arbitrary code in the context of the affected component.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the WLAN chipset modelDetermine the specific Qualcomm chipset used in the device by checking hardware specifications, device documentation, or by querying the system (e.g., via lspci, at commands, or manufacturer specs)Affected if The chipset matches one of the following: Apq8098, Ipq5018, Ipq6018, Ipq8074, Kamorta, Msm8998, Nicobar, or Qca6390
-
Confirm WLAN firmware versionRetrieve the currently installed WLAN firmware version using vendor-specific commands or diagnostic tools (e.g., at+ver, firmware version in /proc, or OEM diagnostic interface)Affected if Any firmware version is returned, since all versions of the affected chipsets are vulnerable
-
Verify WLAN TCP/IP stack is enabledCheck if the WLAN interface is active and the TCP/IP verification component is operational. This can be done by confirming the WLAN driver is loaded and the network interface is up (e.g., ifconfig wlan0, ip link show)Affected if The WLAN interface is present and active, indicating the vulnerable TCP/IP verification component is running
-
Check for exposed WLAN management interfacesInspect whether the device exposes WLAN management or control interfaces (e.g., Wi-Fi daemon status, hostapd, or other WLAN management services) that could receive malicious TCP/IP packetsAffected if WLAN management services are running and accessible, creating a potential attack vector for the buffer overflow
If the device contains any of the listed Qualcomm chipsets (Apq8098, Ipq5018, Ipq6018, Ipq8074, Kamorta, Msm8998, Nicobar, Qca6390) and has WLAN functionality enabled, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply firmware updates provided by the device manufacturer that address this vulnerability. Since this is a low-level WLAN firmware issue, contact the OEM or chipset vendor for patched firmware versions.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3669 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-3669 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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