dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2024-21477

HIGH · 7.5 CVSS v3.1 Published 2024-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Transient DOS while parsing a protected 802.11az Fine Time Measurement (FTM) frame.

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 confidence

This is a denial-of-service vulnerability in the parsing logic for 802.11az Fine Time Measurement (FTM) frames. When the system processes a 'protected' (encrypted/authenticated) FTM frame, a flaw in the parsing routine causes a transient crash or hang, making Wi-Fi functionality temporarily unavailable. The vulnerability stems from improper handling of security-wrapped FTM frames.

MitigationApply vendor-supplied firmware or driver updates that address the 802.11az FTM parsing vulnerability. As a temporary measure, disable 802.11az FTM capabilities if not required, or restrict Wi-Fi exposure to trusted networks to reduce attack surface.

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 data
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Csr8811 FirmwareOperating system
Affected:all versions
Fastconnect 6200 FirmwareOperating system
Affected:all versions
Fastconnect 6800 FirmwareOperating system
Affected:all versions
Fastconnect 6900 FirmwareOperating system
Affected:all versions
Fastconnect 7800 FirmwareOperating system
Affected:all versions
Immersive Home 214 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Wi-Fi hardware and firmware model
    Check system hardware specifications, device manager, or network adapter details to determine if the Wi-Fi chipset is one of: Qualcomm Aqt1000, Ar8035, Csr8811, Fastconnect 6200, Fastconnect 6800, Fastconnect 6900, Fastconnect 7800, or Immersive Home 214. Use commands like 'lspci -v', 'lsusb', or check the router/modem firmware information.
    Affected if The hardware is any of the listed Qualcomm chipsets or firmware variants.
  2. Confirm 802.11az FTM support is present
    Check if the wireless device or firmware supports 802.11az Fine Time Measurement. This may be visible in driver details, firmware capabilities, or wireless configuration interfaces. Look for FTM, Fine Time Measurement, or 802.11az in feature listings.
    Affected if The device firmware or driver advertises 802.11az FTM support or capabilities.
  3. Verify FTM processing is enabled
    Inspect wireless configuration settings on the device or access point to determine if FTM frame processing is active. Check for settings related to FTM responder, FTM initiator, or location services that involve FTM. On Linux, use 'iw list' to check supported features.
    Affected if FTM functionality is enabled and the system will process incoming FTM frames.
  4. Check for protected FTM frame handling
    Review network traffic captures or firmware debug logs if available, looking for evidence of protected (encrypted/authenticated) FTM frames being received. The vulnerability triggers specifically when processing protected FTM frames.
    Affected if The system processes protected FTM frames from untrusted sources.

A system is affected if it uses any of the listed Qualcomm chipsets with 802.11az FTM functionality enabled and can receive protected FTM frames from network peers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware or driver updates that address the 802.11az FTM parsing vulnerability. As a temporary measure, disable 802.11az FTM capabilities if not required, or restrict Wi-Fi exposure to trusted networks to reduce attack surface.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
31.0 hours of engineering $5,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,640.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21477 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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