CVE-2021-30260
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 Integer overflow to buffer overflow issue can occur due to improper validation of input parameters when extscan hostlist configuration command is received 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 confidenceInteger overflow vulnerability in the extscan hostlist configuration command processing due to improper validation of input parameters. The overflow occurs when input parameters are not properly validated before being used in size calculations, potentially allowing an attacker to cause a buffer overflow condition.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 the chipset modelDetermine the exact Qualcomm APQ chipset variant in your device through system information, device specifications, or bootloader/boot messages (e.g., dmesg, /proc/cpuinfo, or vendor diagnostic tools)Affected if The device uses Apq8009, Apq8017, Apq8053, Apq8064au, Apq8076, Apq8092, Apq8094, or Apq8096au
-
Locate the extscan componentSearch for extscan-related binaries, modules, or services in the firmware image or running system (e.g., grep -r extscan /vendor, ls /system/bin/*extscan*, or review vendor documentation for extscan module presence)Affected if The extscan hostlist configuration module is present on the device
-
Verify extscan hostlist interface accessibilityCheck whether the extscan hostlist configuration interface is exposed and accessible (review network exposure, debug interfaces, or administrative interfaces that expose extscan commands; check for any listening services that handle hostlist configuration)Affected if The extscan hostlist command processing interface is accessible to untrusted parties
-
Review input handling for extscan commandsIf you have access to the extscan interface or its configuration files, inspect how hostlist parameters are processed and whether length/size parameters are validated before use in memory operationsAffected if Input parameters to extscan hostlist commands are not validated for integer overflow conditions before size calculations
A device is affected if it contains a Qualcomm APQ chipset from the affected list and has the extscan hostlist configuration interface accessible, since all firmware versions of these chipsets contain the 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-supplied firmware updates from Qualcomm for affected Snapdragon products. Until the patch is available, restrict access to the extscan hostlist configuration interface to trusted parties only.
- Consultation16.0 h
- Testing24.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 $13,184.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30260 — 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-2021-30260 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