CVE-2023-33095
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 multiple payload container type with incorrect container length received in DL NAS transport OTA in NR.
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 in 5G New Radio (NR) where processing Downlink (DL) NAS transport over-the-air messages containing multiple payload container types with incorrect container lengths causes the device to crash or become unresponsive.
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 modelCheck system logs, lspci, or device specifications for Qualcomm modem/chip model (315 5G IoT Modem, Ar8035, Fastconnect 6200/6700/6800/6900/7800, Qca6174a)Affected if Any of these Qualcomm components are present in the environment
-
Check firmware versionQuery the modem or network chip firmware version via vendor-specific tools (e.g., at commands for modems, ethtool for network adapters, or vendor diagnostic interfaces)Affected if Firmware version is present and matches an affected Qualcomm component listed, unless vendor patch has been applied
-
Verify 5G NR capability is enabledCheck if the device has 5G NR radio/connection capability active - look for 5G NR interfaces, modem status showing NR mode, or network registration to 5G cellsAffected if 5G NR functionality is enabled and the device can process DL NAS transport messages
-
Monitor for crash or unresponsiveness eventsReview system logs, kernel logs, modem crash dumps, or network equipment logs for sudden resets, crashes, or service interruptions potentially linked to malformed NAS transport messagesAffected if Unexpected crashes or unresponsiveness occur on the Qualcomm component, especially when 5G NR is active
-
Check for vendor security advisoriesConsult Qualcomm's security advisories or the device vendor's documentation for CVE-2023-33095 and any available patch informationAffected if No patch has been applied to the affected Qualcomm firmware
If the environment contains any of the listed unpatched Qualcomm components with 5G NR capability enabled, the device is potentially affected by this NAS transport message handling denial of service vulnerability.
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/software patches for 5G NR baseband or network equipment once released; until then, monitor for service disruptions from malformed NAS transport messages.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33095 — 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-33095 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