dbcve.org
Qca6574au FirmwareOperating system · Qualcomm

CVE-2024-33064

HIGH · 8.2 CVSS v3.1 Published 2024-10-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Information disclosure while parsing the multiple MBSSID IEs from the beacon.

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 an information disclosure vulnerability in Wi-Fi device firmware where parsing multiple MBSSID (Multiple Basic Service Set Identifier) Information Elements from beacon frames allows an attacker to potentially obtain sensitive information. MBSSID is used in 802.11ax (Wi-Fi 6) environments to enable multiple virtual APs from a single radio, and improper handling of these IEs during beacon parsing leads to the leak.

MitigationApply vendor-provided firmware updates that address the MBSSID IE parsing vulnerability; until patches are available, consider reducing MBSSID complexity or isolating affected access points from untrusted networks.

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
Qca6574au FirmwareOperating system
Affected:all versions
Qca6574a FirmwareOperating system
Affected:all versions
Qca6564au FirmwareOperating system
Affected:all versions
Qca6564a FirmwareOperating system
Affected:all versions
Mdm9628 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
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L

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 the Wi-Fi chipset model
    Access the access point or wireless router admin interface and look under System Information, Wireless Settings, or Hardware Details to find the chipset or platform model number. Alternatively, use commands like 'lspci' (for PCIe cards), 'lsusb' (for USB adapters), or check /proc/cpuinfo on embedded devices.
    Affected if The chipset model matches Qca6574au, Qca6574a, Qca6564au, Qca6564a, or Mdm9628 (any firmware version).
  2. Check if MBSSID is enabled
    Log into the wireless access point admin panel and navigate to Wireless Settings, Wireless Networks, or Advanced Wireless settings. Look for options labeled 'MBSSID', 'Multi-BSSID', 'Multiple SSID', 'Virtual AP', or 'VAP' and verify whether any MBSSID profiles are configured or enabled.
    Affected if MBSSID feature has one or more profiles configured and enabled on the device.
  3. Verify 802.11ax (Wi-Fi 6) operation mode
    In the wireless settings, check the wireless mode, 802.11 mode, or radio settings. Confirm whether the device is set to 802.11ax, Wi-Fi 6, or a mixed mode that includes 802.11ax (such as 'ax/n/g' or 'Wi-Fi 6/6E').
    Affected if The device operates in 802.11ax mode or a mixed mode that includes 802.11ax, as MBSSID is primarily an 802.11ax feature.
  4. Inspect beacon frame MBSSID Information Elements
    Use a wireless sniffer tool such as Wireshark, Kismet, or airmon-ng to capture beacon frames from the access point. Analyze the captured frames for Multiple BSSID IE (vendor-specific IE with OUI 00:0F:AC or infrastructure element ID 12) and verify if multiple SSIDs are advertised in the beacons.
    Affected if Captured beacon frames contain multiple MBSSID Information Elements indicating active use of this feature.

The environment is affected if the device uses any of the listed Qualcomm chipsets (Qca6574au, Qca6574a, Qca6564au, Qca6564a, or Mdm9628) and has MBSSID enabled while operating in 802.11ax mode, as all firmware versions of these chipsets contain the parsing vulnerability.

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-provided firmware updates that address the MBSSID IE parsing vulnerability; until patches are available, consider reducing MBSSID complexity or isolating affected access points from untrusted networks.

Fix this in Qca6574au Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33064 — 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-33064 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