dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2023-28566

MEDIUM · 5.5 CVSS v3.1 Published 2023-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 in WLAN HAL while handling the WMI state info command.

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 the WLAN (Wireless LAN) Hardware Abstraction Layer that occurs when processing WMI (Wireless/Media Interface) state info commands. The vulnerability allows unauthorized exposure of sensitive information through improper handling of state data returned by WMI commands.

MitigationApply vendor-supplied firmware updates for affected wireless devices. Until patches are available, monitor network traffic for anomalous behavior and restrict physical proximity to untrusted wireless sources.

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
Csrb31024 FirmwareOperating system
Affected:all versions
Fastconnect 6200 FirmwareOperating system
Affected:all versions
Fastconnect 6700 FirmwareOperating system
Affected:all versions
Fastconnect 6800 FirmwareOperating system
Affected:all versions
Fastconnect 6900 FirmwareOperating system
Affected:all versions
Qca6310 FirmwareOperating system
Affected:all versions
Qca6320 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 wireless hardware vendor and model
    On the target system, run commands such as 'lspci -v' (Linux) or check Device Manager (Windows) to list installed wireless adapters. Look for Qualcomm Aqt1000, Csrb31024, Fastconnect 6200/6700/6800/6900, Qca6310, or Qca6320 in the adapter description or chip details.
    Affected if The system has any of the listed Qualcomm wireless chips: Aqt1000, Csrb31024, Fastconnect 6200, Fastconnect 6700, Fastconnect 6800, Fastconnect 6900, Qca6310, or Qca6320.
  2. Check wireless firmware version
    If a Qualcomm wireless adapter is identified, retrieve the firmware version using vendor-specific tools (such as 'iw list', 'ath10k-firmware-reader', or manufacturer diagnostic utilities). Compare the firmware version string against the affected product list.
    Affected if The firmware version corresponds to any of the affected Qualcomm products listed (all versions of Aqt1000, Csrb31024, Fastconnect 6200/6700/6800/6900, Qca6310, Qca6320).
  3. Verify WMI/WLAN interface status
    Check if the wireless interface is active and WMI command processing is enabled. On Linux, use 'ip link show' or 'iw dev' to check interface state. On Windows, check wireless adapter status in Device Manager or via 'netsh wlan show interfaces'.
    Affected if The wireless interface is enabled and actively processing WMI state info commands, which is the normal operating state for affected devices.
  4. Review system and wireless driver logs
    Examine system logs (such as /var/log/messages, dmesg, or Windows Event Viewer under System/Application logs) for any unusual WMI-related errors or information disclosure indicators related to wireless state data.
    Affected if Logs show anomalous WMI state info handling or unexpected information exposure events from the wireless subsystem.

If your system contains any of the affected Qualcomm wireless chips (Aqt1000, Csrb31024, Fastconnect 6200/6700/6800/6900, Qca6310, Qca6320) and has the wireless interface enabled, you are potentially affected since all firmware versions of these products are vulnerable to information disclosure via improper WMI state data handling.

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 updates for affected wireless devices. Until patches are available, monitor network traffic for anomalous behavior and restrict physical proximity to untrusted wireless sources.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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