dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2023-28559

HIGH · 7.8 CVSS v3.1 Published 2023-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Memory corruption in WLAN FW while processing command parameters from untrusted WMI payload.

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

Memory corruption vulnerability in WLAN firmware during processing of command parameters from untrusted WMI (Wireless Management Interface) payloads. The flaw allows an attacker to trigger memory corruption via malicious WMI commands, potentially leading to code execution or denial of service.

MitigationApply vendor-supplied firmware updates for affected WLAN devices; until patches are available, consider network segmentation to limit exposure to untrusted wireless clients.

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
Ar8031 FirmwareOperating system
Affected:all versions
Ar9380 FirmwareOperating system
Affected:all versions
Csr8811 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions
Csra6640 FirmwareOperating system
Affected:all versions
Fastconnect 6200 FirmwareOperating system
Affected:all versions
Fastconnect 6700 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
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 checks

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

  1. Identify the WLAN hardware in the system
    Run commands such as 'lspci | grep -i wireless', 'lspci | grep -i network', 'lsusb', or check Device Manager on Windows to list wireless network adapters. Look for Qualcomm chipsets matching the affected list: Aqt1000, Ar8031, Ar9380, Csr8811, Csra6620, Csra6640, Fastconnect 6200, or Fastconnect 6700.
    Affected if The system contains any of the listed Qualcomm WLAN chips (Aqt1000, Ar8031, Ar9380, Csr8811, Csra6620, Csra6640, Fastconnect 6200, or Fastconnect 6700)
  2. Determine the firmware version of the Qualcomm WLAN chip
    On Linux, use 'iw list' or check /lib/firmware/ for the relevant Qualcomm firmware files. On Windows, check the driver details in Device Manager under the wireless adapter properties. Run 'dmesg | grep -i firmware' after boot to see loaded firmware strings.
    Affected if The firmware version cannot be determined or is present (note: all versions of the listed chips are affected)
  3. Verify the WMI interface is accessible
    Check if the wireless device supports and has the WMI (Wireless Management Interface) subsystem active. On Linux, examine output from 'iw list' for WMI support, or check 'ath10k'/'ath11k' driver debugfs if applicable. On Windows, verify the WLAN driver is loaded and the device is functional.
    Affected if The WMI interface is active and the wireless device is functioning (the vulnerability triggers during WMI command processing)
  4. Assess exposure to untrusted WMI payloads
    Review network configuration to determine if the wireless interface accepts connections from untrusted or unknown clients. Check if the device is operating in AP/mesh mode, or if it connects to untrusted networks. Examine firewall rules for wireless interfaces.
    Affected if The device accepts wireless connections from untrusted clients, operates as an AP, or processes WMI commands from external/untrusted sources

You are affected if your system contains any of the listed Qualcomm WLAN chips (Aqt1000, Ar8031, Ar9380, Csr8811, Csra6620, Csra6640, Fastconnect 6200, Fastconnect 6700) and the WMI interface is active and exposed to untrusted wireless traffic.

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 WLAN devices; until patches are available, consider network segmentation to limit exposure to untrusted wireless clients.

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-28559 — 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-28559 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