CVE-2023-33015
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 · uneditedTransient DOS in WLAN Firmware while interpreting MBSSID IE of a received beacon 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 confidenceA denial of service vulnerability exists in WLAN firmware when parsing the Multiple BSSID (MBSSID) Information Element from a received beacon frame. An attacker can send a specially crafted beacon frame containing a malformed MBSSID IE to trigger a transient crash or hang in the affected wireless device, causing availability disruption.
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 wireless chipset modelCheck your device's hardware specifications, network adapter details, or system firmware inventory to determine the Qualcomm wireless chip in use (e.g., Fastconnect 6200, Ar9380, etc.)Affected if The chipset matches any of the following: Qualcomm 315 5g, Aqt1000, Ar8035, Ar9380, Csr8811, Csrb31024, Fastconnect 6200, or Fastconnect 6700
-
Verify firmware versionAccess the wireless device management interface or firmware dump to retrieve the installed firmware version string for the identified chipsetAffected if Any firmware version is present (the advisory states all versions are affected)
-
Confirm WLAN functionality is activeCheck if the wireless interface is enabled and operational via network status, driver status, or wireless adapter settingsAffected if WLAN is enabled and capable of receiving beacon frames - the vulnerable code path executes when the device parses incoming beacon frames
If your device uses any of the listed Qualcomm chipsets and has WLAN enabled, you are vulnerable to CVE-2023-33015 because all firmware versions of these chipsets contain the flaw when parsing MBSSID Information Elements.
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-supplied firmware updates to affected wireless devices; until patches are available, consider network segmentation and monitoring for anomalous beacon frames.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33015 — 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-2023-33015 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