CVE-2023-24843
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 in Modem while triggering a camping on an 5G cell.
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 cellular modem firmware where triggering a camping connection to a 5G cell causes the modem to become temporarily unresponsive. The issue likely stems from improper state handling or race conditions in the 5G cell acquisition process, leading to a temporary loss of modem functionality until reset or reconnection.
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 installed Qualcomm modem hardwareExamine system logs, hardware inventory, or use modem diagnostic commands (such as 'at+qcmap' or manufacturer-specific status queries) to identify the exact modem model and firmware package in useAffected if The hardware matches any of the following: Qualcomm 315 5G IoT Modem, Qualcomm Ar8035, Qualcomm Fastconnect 6200/6700/6800/6900/7800, or Qualcomm Qca6391
-
Determine if 5G connectivity is activeCheck the modem's network status and connection logs to see if the device is currently connected to or attempting to connect to a 5G networkAffected if 5G network mode or 5G radio is enabled and the modem is registered on a 5G cell
-
Verify 5G cell camping configurationReview modem configuration settings for cell camping parameters, typically found in modem AT commands (such as 'at+cellsrch' or similar vendor-specific commands) or in the network registration settingsAffected if 5G cell camping is enabled or configured on the modem
-
Look for modem unresponsiveness eventsMonitor system and network logs for signs of temporary modem failure including: connection timeouts, unexpected resets, loss of modem communication, or inability to transmit/receive data until a reset or reconnection occursAffected if The modem exhibits periodic or triggered episodes of unresponsiveness that resolve only after reset or reconnection, particularly after initiating 5G cell camping
A system is affected if it uses any of the listed Qualcomm modem firmware products, has 5G cell camping enabled, and demonstrates temporary modem unresponsiveness episodes when 5G connections are attempted.
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-supplied firmware updates for affected modem hardware. If no patch is available, implement network-level redundancy or fallback to 4G LTE to maintain connectivity during modem DOS events.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24843 — 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-24843 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