CVE-2020-11263
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 · uneditedAn integer overflow due to improper check performed after the address and size passed are aligned in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, 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 confidenceInteger overflow vulnerability in Qualcomm Snapdragon chips where improper validation occurs after address and size alignment checks. This could allow memory corruption or out-of-bounds memory access, potentially leading to code execution or denial of service.
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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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 affected Qualcomm chips in the environmentExamine system hardware listings, network adapter details, or device inventory to determine if any of the following chips are present: Ar8035, Qca6390, Qca6391, Qca6426, Qca6436, Qca8337, Qca9984, or Qcm2290. These are typically found in network interface cards, WiFi adapters, or embedded devices.Affected if Any of the listed Qualcomm chips or firmware components are present in the system
-
Check firmware version of Qualcomm network or wireless chipsUse system utilities such as 'ethtool -i', 'lspci', 'lsusb', or chip-specific diagnostic tools to query the firmware version of the identified Qualcomm components. For embedded devices, consult the device firmware or bootloader information.Affected if The firmware version cannot be determined or is any version (note: all versions of these firmware products are affected)
-
Verify if vulnerable memory alignment code path is activeThis vulnerability resides in the firmware-level memory alignment validation logic. Check if the Qualcomm chip is actively processing network traffic or memory operations that would trigger the alignment checks. Monitor chip activity or examine firmware configuration if diagnostic access is available.Affected if The chip is operational and handling memory operations (the vulnerability is present in all versions when the chip is active)
If any of the affected Qualcomm firmware products (Ar8035, Qca6390, Qca6391, Qca6426, Qca6436, Qca8337, Qca9984, Qcm2290) are present and operational in the environment, the system is considered affected since all versions of these firmwares contain the integer overflow 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 vendor-provided firmware updates from Qualcomm and device manufacturers to address the integer overflow in the memory alignment validation logic.
- Consultation8.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 $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11263 — 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-11263 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