CVE-2020-11213
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 reads might occur in while processing Service descriptor due to improper validation of length of fields 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 Wearables, 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 Service descriptor processing across multiple Snapdragon product lines. The vulnerability stems from improper validation of field lengths during Service descriptor parsing, allowing memory access beyond allocated boundaries.
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 device chipset modelCheck the system's hardware information to determine the Snapdragon chipset in use. On Linux, run 'cat /proc/cpuinfo' or check 'dmesg' boot logs. On Android, check 'Settings > About Phone' or use 'getprop' commands.Affected if The chipset model matches Apq8009, Apq8009w, Apq8016, Apq8017, Apq8037, Apq8039, Apq8052, or Apq8053.
-
Verify Service descriptor processing is activeDetermine if the device exposes services that use Service descriptor parsing. This is typically handled by the baseband processor or modem subsystem. Check running services or diagnostic interfaces that process service-related data.Affected if The device has active service processing components that handle Service descriptor parsing from external inputs.
-
Confirm firmware versionQuery the current firmware version of the Snapdragon component. On Android, use 'getprop' for radio or baseband version. For embedded devices, check vendor documentation or access the bootloader/BMC to retrieve firmware build information.Affected if The firmware is any version running on an affected APQ chipset, since all versions of these products are vulnerable.
-
Assess network exposureReview network configuration to determine if the affected chipset has open network interfaces that could receive malicious Service descriptor data. Check firewall rules, exposed ports, and network service listeners.Affected if The device accepts Service descriptor data over network interfaces without filtering or validation.
If the device uses any of the listed Snapdragon APQ chipsets (8009, 8009w, 8016, 8017, 8037, 8039, 8052, 8053) and processes Service descriptors from untrusted sources, the environment is affected by CVE-2020-11213.
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 patches/firmware updates for affected Snapdragon components. Until patches are available, network segmentation may reduce exposure for affected devices.
- 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-11213 — 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-11213 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