CVE-2023-33045
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 · uneditedMemory corruption in WLAN Firmware while parsing a NAN management frame carrying a S3 attribute.
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 confidenceMemory corruption vulnerability in WLAN firmware during parsing of NAN (Neighbor Awareness Networking) management frames containing a specially crafted S3 attribute. The parsing logic fails to properly validate or bound-check the S3 attribute data, leading to heap or stack corruption that could enable remote code execution.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the WiFi chipset modelCheck the device documentation, router admin interface, or system information to determine the specific Qualcomm WLAN chipset or firmware in use (examples: Ar8035, Csr8811, Qca6390, Wcn685x, Wcn785x, Immersive Home 214 Platform)Affected if The chipset or firmware matches one of the affected products listed in the CVE (Ar8035, Csr8811, Qca6390, Wcn685x 5, Wcn685x 1, Wcn785x 1, Wcn785x 5, or Immersive Home 214 Platform)
-
Confirm NAN feature is enabledAccess the WiFi settings on the device (router, access point, or endpoint) and verify whether Neighbor Awareness Networking (NAN) or similar peer-to-peer Wi-Fi discovery feature is turned onAffected if NAN functionality is currently enabled in the Wi-Fi configuration settings
-
Check firmware version detailsLocate the firmware version information in the device admin interface, system diagnostics, or through vendor-specific commands (such as 'iw list', 'wl -v', or device-specific queries)Affected if The firmware version corresponds to any of the affected Qualcomm chipsets listed (all versions are affected per the CVE)
-
Inspect wireless driver logsReview system or kernel logs for wireless subsystem messages related to NAN processing, or capture wireless traffic to observe NAN management frame handlingAffected if The device processes NAN discovery or service discovery frames and the chipset matches the affected product list
A user is affected if their device uses any of the listed Qualcomm WLAN chipsets/firmware AND has NAN functionality enabled, as the vulnerability requires NAN frame parsing to be triggered.
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-provided firmware updates for affected WLAN chipsets and devices. Until patches are available, consider disabling NAN functionality in Wi-Fi settings to reduce attack surface.
- Consultation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33045 — 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-33045 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