CVE-2023-33100
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 DL NAS Transport message when message ID is not defined in the 3GPP specification.
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 processing of Downlink (DL) NAS Transport messages. When a message containing a Message ID that is not defined in the 3GPP specification is received, the device fails to handle it gracefully, causing a transient denial of service. This indicates insufficient input validation or error handling for undefined protocol elements.
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 network chipset or WiFi adapter modelCheck device specifications, lspci output for network devices, or lsusb for USB无线 adapters. Look for Qualcomm product names: Ar8035, QCA6174a, QCA6584au, QCA6698aq, QCA8081, or Fastconnect 6700/6900/7800.Affected if The device uses any of the listed Qualcomm chips or firmware modules.
-
Check firmware or driver version stringFor WiFi adapters, use 'iw list' or 'lspci -v' to retrieve firmware version information. For cellular/baseband, check AT command outputs or manufacturer firmware release notes.Affected if The firmware version string matches any of the affected products (Ar8035, Fastconnect 6700/6900/7800, Qca6174a, Qca6584au, Qca6698aq, Qca8081).
-
Identify NAS Transport message handling capabilityDetermine if the device implements NAS (Non-Access Stratum) protocol stack, typically found in cellular modems or WiFi 6/6E/7 devices using Qualcomm Fastconnect. This can be confirmed by checking if the device processes 3GPP NAS messages.Affected if The device processes DL NAS Transport messages as part of its normal cellular or WiFi operation.
-
Verify if the device accepts external DL NAS messagesInspect network logging or protocol traces (using Wireshark or cellular protocol analyzers) for DL NAS Transport message processing. Check if the device can receive NAS messages from the network infrastructure.Affected if The device processes DL NAS Transport messages from the network without filtering or validating Message IDs against the 3GPP specification.
A device is affected if it runs any version of the listed Qualcomm firmware (Ar8035, Fastconnect 6700/6900/7800, Qca6174a, Qca6584au, Qca6698aq, Qca8081) and processes DL NAS Transport messages from the network.
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 validation and error handling for DL NAS Transport messages with undefined Message IDs, ensuring the device can safely reject or ignore malformed messages without crashing or becoming unresponsive.
- 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-33100 — 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-33100 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