CVE-2020-11169
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 over-read while processing received L2CAP packet due to lack of integer overflow check' 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 APQ8009, APQ8053, QCA6390, QCN7605, QCN7606, SA415M, SA515M, SA6155P, SA8155P, SC8180X, SDX55
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 confidenceBuffer over-read vulnerability in the Bluetooth L2CAP packet processing code within Qualcomm Snapdragon chipset firmware. The flaw stems from a missing integer overflow check when processing received L2CAP packets, allowing an attacker to read beyond allocated buffer boundaries and potentially access sensitive memory contents. This is a baseband/firmware-level flaw affecting multiple Snapdragon platforms.
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 Qualcomm chipset modelCheck the device specifications, system information, or bootloader strings to determine if the chipset matches any of the following: Apq8009, Apq8053, Qca6390, Qcn7605, Qcn7606, Sa415m, Sa515m, Sa6155pAffected if The device uses any of the listed Qualcomm chipset models
-
Determine the firmware versionQuery the device's baseband or Bluetooth firmware version through system settings, about phone page, or AT command interface (if accessible). Compare the installed version against the affected product list which states all versions are vulnerableAffected if The firmware version is any version of the listed chipsets (all versions are affected)
-
Check if Bluetooth is enabled and activeInspect whether Bluetooth functionality is turned on in the device settings or via system commandsAffected if Bluetooth is enabled, as the vulnerability exists in L2CAP packet processing which is active during Bluetooth communication
-
Verify patch status through system updatesCheck for available system or security updates from the device OEM, and review the patch notes or security bulletins for mentions of CVE-2020-11169 or Qualcomm security advisoriesAffected if No patch addressing this CVE has been applied and the device runs an unpatched firmware version
A user is affected if their device contains any of the listed Qualcomm chipsets (Apq8009, Apq8053, Qca6390, Qcn7605, Qcn7606, Sa415m, Sa515m, Sa6155p) with unpatched firmware and has Bluetooth enabled
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 Qualcomm-provided firmware/security patches through device OEM channels; users should check for and apply available system updates. Given this is a firmware-level vulnerability in embedded chipsets, affected devices may require vendor-specific patches or potential hardware replacement if no update is available.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.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 $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11169 — 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-11169 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