CVE-2023-33104
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 processing PDU Release command with a parameter PDU ID out of range.
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 · high confidenceA denial of service vulnerability exists in PDU Release command processing where the PDU ID parameter is not validated before use. When an out-of-range PDU ID is provided, it likely causes an access violation or unhandled exception, resulting in a transient service 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 Qualcomm hardware in the systemCheck network adapters, wireless cards, or modem devices. On Windows, run 'netsh wlan show interfaces' or check Device Manager. On Linux, check 'lspci' or 'lsusb' for Qualcomm wireless/modem devices.Affected if Any of the following devices are present: Qualcomm 315 5G IoT Modem, Qualcomm Ar8035, Qualcomm Fastconnect 6200/6700/6800/6900/7800, or Qualcomm Qca6174a.
-
Determine the firmware version of the Qualcomm deviceUse vendor-specific tools or commands to query the firmware version. For Fastconnect devices, check via 'netsh wlan show drivers' or the wireless adapter properties. For modems, use AT commands or the Qualcomm QE utility.Affected if The device firmware matches any of the affected product lines (all versions are affected per the advisory).
-
Verify PDU Release command processing is activeMonitor network or modem activity logs for PDU Release command usage. This is typically relevant in 5G/IoT modem contexts. Check system event logs or modem diagnostic logs for PDU-related operations.Affected if PDU Release commands are being processed by the affected firmware, as the vulnerability triggers when an out-of-range PDU ID is received.
-
Review for crash or service disruption eventsCheck system event logs, modem crash dumps, or kernel logs for access violations or unhandled exceptions occurring around the time of PDU operations.Affected if Unexpected crashes, access violations, or service disruptions occur when PDU Release commands are processed, indicating potential exploitation.
A system is affected if it contains any of the listed Qualcomm devices (315 5G IoT Modem, Ar8035, Fastconnect 6200/6700/6800/6900/7800, or Qca6174a) and uses PDU Release command processing functionality.
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 dataImplement proper bounds checking on the PDU ID parameter before processing the Release command to ensure it falls within valid ranges.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33104 — 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-33104 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