CVE-2023-33080
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 while parsing a vender specific IE (Information Element) of reassociation response management 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 the parsing logic for vendor-specific Information Elements (IE) within reassociation response management frames. When a malformed or specially crafted vendor-specific IE is processed, the parsing routine fails to handle the data correctly, causing a transient DoS condition. This affects wireless networking software or firmware that processes 802.11 reassociation responses.
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 hardware model and firmware packageRetrieve the device inventory or firmware version using `cat /proc/cpuinfo`, `固件版本` in system info, or check the hardware label/schematics for the Qualcomm chipset model number (e.g., 315, 9206, APQ8017, APQ8064AU, AQT1000, AR8031, AR8035, AR9380)Affected if The device uses one of the listed Qualcomm chipset models and the firmware version cannot be determined or is prior to a vendor patch
-
Locate the wireless firmware versionCheck the wireless interface firmware using `iw list`, `wpa_supplicant -v`, or look in `/lib/firmware/` for the relevant Qualcomm wireless firmware files (often named with the chipset or module identifier)Affected if The firmware file version cannot be verified as patched or the installed firmware version string is unknown
-
Confirm the device operates as a WiFi clientVerify the device is configured to act as a WiFi client (STA mode) by checking `iwconfig`, `iw dev`, or network manager settings for active wireless client interfacesAffected if The device functions as a WiFi client that processes 802.11 reassociation response frames from access points
-
Check vendor security advisoriesSearch the Qualcomm or device vendor security advisory pages for CVE-2023-33080 and note any mentioned fixed firmware versions for your specific modelAffected if No fixed firmware version is listed or your current version predates the advisory date
You are affected if your device runs any of the listed Qualcomm firmware variants (315 5G IoT, 9206 LTE, APQ8017, APQ8064AU, AQT1000, AR8031, AR8035, AR9380) as a WiFi client and lacks a vendor patch for CVE-2023-33080.
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 patches or firmware updates that address the IE parsing vulnerability. Until patches are available, consider network segmentation to limit exposure to untrusted wireless networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33080 — 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-33080 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