CVE-2020-11276
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 · uneditedPossible buffer over read while processing P2P IE and NOA attribute of beacon and probe response frames due to improper validation of P2P IE and NOA attribute lengths in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking
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 confidenceA buffer overread vulnerability exists in the Wi-Fi P2P (Peer-to-Peer) processing code within Qualcomm Snapdragon chipsets. The vulnerability occurs when parsing P2P Information Elements (IE) and NOA (Notice of Absence) attributes in beacon and probe response frames. Due to improper validation of length fields before reading data, the device can read beyond the allocated buffer boundaries, potentially allowing remote code execution or information disclosure.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the chipset modelCheck the device specifications, about page, or system information to determine the exact Qualcomm Snapdragon chipset model (e.g., Apq8009, Apq8017, Apq8053, Apq8064au, Apq8076, Apq8084, Apq8092, or Apq8094)Affected if The device uses any of the listed chipset models (Apq8009, Apq8017, Apq8053, Apq8064au, Apq8076, Apq8084, Apq8092, or Apq8094)
-
Check if Wi-Fi P2P is enabledNavigate to device Wi-Fi settings and look for Wi-Fi Direct or P2P functionality. On Android, check Settings > Wi-Fi > Wi-Fi Direct. On Linux/embedded systems, check if the P2P interface is configured or active using 'iw list' or 'wpa_cli status'Affected if Wi-Fi P2P (also known as Wi-Fi Direct) is turned on or has been used on the device
-
Verify firmware versionAccess the device firmware or baseband version information. On Android, check Settings > About Phone > Build Number or Baseband version. For embedded devices, consult the vendor documentation or access the firmware image directlyAffected if The firmware version cannot be confirmed as patched by the vendor, or the device is running vendor firmware prior to the patch release date
A device is affected if it uses any of the listed Qualcomm Snapdragon chipsets (Apq8009 through Apq8094) and has Wi-Fi P2P functionality enabled, with unpatched firmware.
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 vendor-supplied firmware patches from Qualcomm and device manufacturers. As an interim mitigation, consider disabling Wi-Fi P2P functionality on affected devices until patches can be deployed.
- Consultation8.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11276 — 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-11276 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