CVE-2023-33096
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, as specified in 3GPP 24.501 v16.
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 transient Denial of Service vulnerability exists in the processing of Downlink (DL) NAS (Non-Access Stratum) Transport messages as defined in 3GPP 24.501 v16. The vulnerability allows an attacker to cause a temporary service disruption by sending specially crafted DL NAS Transport messages to a affected device implementing the 3GPP NAS protocol.
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 315 5G IoT modem usageCheck system for presence of Qualcomm 315 5G modem: On Linux, run 'lsusb' or check 'AT+CGMR' via serial AT command interface if the device has a cellular modem. On Windows, check Device Manager under Modems or Network adapters.Affected if A Qualcomm 315 5G IoT modem is present in the system.
-
Identify Qualcomm Fastconnect WiFi chip usageCheck system for presence of Fastconnect chips (6200/6700/6800/6900/7800): On Linux, run 'lspci' or 'lsusb' and look for Qualcomm Atheros wireless adapters. Check WiFi driver info via 'iw list' or 'lshw -C network'.Affected if A Qualcomm Fastconnect 6200, 6700, 6800, 6900, or 7800 wireless adapter is present.
-
Identify Qualcomm QCA6174a WiFi chip usageCheck system for QCA6174a: Run 'lspci | grep -i qualcomm' or 'lspci | grep -i atheros' on Linux. Check wireless adapter model in Device Manager on Windows.Affected if A Qualcomm QCA6174a wireless adapter is present.
-
Identify Qualcomm AR8035 usageCheck networking equipment for AR8035 PHY: Run 'ethtool -i <interface>' on Linux or check router/switch firmware diagnostics for ethernet PHY information.Affected if A device with Qualcomm AR8035 ethernet PHY is present.
-
Verify 3GPP NAS protocol implementationDetermine if the device implements 3GPP NAS (Non-Access Stratum) protocol: This applies to cellular modems operating on 4G LTE or 5G networks. Check if the device connects to cellular networks (e.g., check 'nmcli' or 'ip link' for cellular interfaces).Affected if The device is a cellular modem or UE (User Equipment) connecting to 4G/5G networks using NAS protocol.
The user is affected if their system contains any of the listed Qualcomm firmware components (315 5G IoT modem, Fastconnect series WiFi chips, QCA6174a, or AR8035) that implement 3GPP NAS protocol for cellular connectivity.
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-specific patches for affected network equipment (likely cellular infrastructure components such as eNodeB/gNodeB, MME, AMF, or UE modems). Until patches are available, implement network segmentation and monitoring for anomalous NAS message patterns.
- 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-33096 — 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-33096 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