CVE-2020-11241
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 · uneditedOut of bound read will happen if EAPOL Key length is less than expected while processing NAN shared key descriptor attribute 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 · moderate confidenceOut-of-bounds read vulnerability in Qualcomm Snapdragon chipsets when processing NAN (Neighbor Awareness Networking) shared key descriptor attributes. The vulnerability triggers when EAPOL Key length is shorter than expected, causing the system to read beyond buffer boundaries and potentially leak sensitive memory contents.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the chipset modelCheck the device specifications, /proc/cpuinfo, or system information to determine the Qualcomm chipset in use. Look for model numbers such as Apq8009, Apq8096au, Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, or Csra6620.Affected if The chipset matches any of the following: Apq8009, Apq8096au, Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, or Csra6620.
-
Verify firmware versionCheck the installed firmware version of the Qualcomm chipset through vendor documentation, device settings, or by querying the firmware directly if access is available. Compare against the affected product list.Affected if All firmware versions of the listed chipsets are affected.
-
Confirm NAN/WiFi Aware feature statusCheck whether Neighbor Awareness Networking (NAN) or WiFi Aware is enabled on the device. This can be found in WiFi settings, network configuration files, or by querying the wireless interface settings using commands such as 'iw list' or checking 'wpa_supplicant' configuration.Affected if NAN/WiFi Aware feature is enabled, as this is the attack surface where the vulnerable NAN shared key descriptor attribute processing occurs.
-
Inspect EAPOL Key handling configurationReview the EAPOL (Extensible Authentication Protocol over LAN) configuration related to NAN or WiFi Aware connections. Check if the device processes EAPOL Key frames in NAN discovery or peer matching contexts.Affected if The device processes EAPOL Key frames within NAN functionality, particularly when the EAPOL Key length field may be shorter than expected by the firmware.
If the device uses any of the affected Qualcomm chipset models (Apq8009, Apq8096au, Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620) and has NAN/WiFi Aware enabled, the environment is potentially affected by this out-of-bounds read 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 device manufacturers or Qualcomm. Since this is a hardware/firmware-level vulnerability in Snapdragon chipsets, no network-level mitigation is available; affected devices require vendor-supplied patches.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11241 — 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-11241 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