CVE-2021-1887
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 assertion can be reached in the WLAN subsystem while using the Wi-Fi Fine Timing Measurement protocol in 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 confidenceA reachable assertion vulnerability exists in the WLAN subsystem when processing Wi-Fi Fine Timing Measurement (FTM) protocol packets. An attacker with proximity to the target network could trigger the assertion, potentially causing a denial of service or unexpected behavior in affected Snapdragon Wired Infrastructure and Networking devices.
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 device chipset or modelCheck the device documentation, CLI output (e.g., 'lspci', 'iw list', or vendor-specific commands), or hardware labeling to determine if the device uses one of the following chipsets: Qualcomm Ar7420, Ar9380, Csr8811, Ipq4018, Ipq4019, Ipq4028, Ipq4029, or Ipq8064Affected if The device implements any of the listed Qualcomm chipsets in its wireless subsystem
-
Verify FTM protocol support is enabledCheck the Wi-Fi configuration or wireless settings via CLI (e.g., 'iw dev', 'hostapd-cli', or vendor management interface) for Fine Timing Measurement or FTM responder/ initiator settingsAffected if FTM (802.11mc) protocol support is enabled or configured on the device
-
Check for FTM-related processes or servicesInspect running processes or services related to Wi-Fi (e.g., 'ps', 'hostapd', 'wpa_supplicant') and look for FTM-specific configuration files or parameters in /etc or /var directoriesAffected if FTM-related services, processes, or configuration entries are found on the device
-
Review wireless interface configurationUse wireless management tools (iw, wpa_supplicant, or vendor CLI) to query the wireless interface capabilities and active parameters, specifically looking for FTM responder or FTM initiator settingsAffected if The wireless interface shows FTM capability or configuration as active
-
Check firmware version if accessibleIf firmware version is exposed via CLI (e.g., 'cat /proc/version', vendor-specific 'show version' or 'get firmware-version'), compare against the affected product listAffected if The device runs firmware on any of the listed Qualcomm chipsets regardless of version, as all versions are affected
A user is affected if their device uses any of the listed Qualcomm chipsets (Ar7420, Ar9380, Csr8811, Ipq4018, Ipq4019, Ipq4028, Ipq4029, Ipq8064) and has FTM protocol support enabled in the wireless configuration.
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 for affected Snapdragon Wired Infrastructure and Networking products. If no patch is available, consider disabling FTM protocol support on vulnerable devices or restricting Wi-Fi access to trusted entities.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1887 — 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-1887 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