CVE-2023-33058
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 · uneditedInformation disclosure in Modem while processing SIB5.
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 critical information disclosure vulnerability exists in the modem component when processing SIB5 (System Information Block 5), which is broadcast in LTE/5G networks to provide neighbor cell information. An attacker with network adjacency could potentially intercept or manipulate SIB5 processing to expose sensitive information from the modem's memory or operations.
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
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 modem hardware in the environmentInventory network or wireless hardware to determine if any devices contain the affected Qualcomm modem chips: Ar8035, Fastconnect 6700, Fastconnect 6900, Fastconnect 7800, Qca6584au, Qca6698aq, Qca8081, or Qca8337. Check device specifications, hardware BOMs, or lspci/mmc output on Linux systems for wireless card identification.Affected if Any device with one of the listed Qualcomm modem chips is present in the environment
-
Retrieve the installed modem firmware versionUse vendor-specific commands to query the modem firmware version. On affected devices, this may include: at commands like AT+CGMR or ATI for cellular modems, firmware version logs from /var/log/messages, or vendor management interfaces that display radio/modem firmware versions. Compare the version string against the affected product list.Affected if The firmware version matches any of the listed affected products (all versions of these firmwares are affected)
-
Confirm LTE or 5G network capability is enabledVerify that the device has active LTE or 5G interfaces configured. Check network interfaces (ip link show), modem manager status, or radio configuration to determine if the device is actively using cellular connectivity that would process SIB5 messages.Affected if LTE or 5G interfaces are active and the device is connected to a cellular network that broadcasts SIB5
-
Check vendor security advisories for patch statusReview the device vendor or Qualcomm security advisory pages to determine if a firmware update addressing CVE-2023-33058 has been released. Note the firmware version of any available update.Affected if No vendor firmware patch addressing this CVE has been applied to the installed modem firmware
A user is affected if their environment contains any device with the listed Qualcomm modem firmware (Ar8035, Fastconnect 6700/6900/7800, Qca6584au, Qca6698aq, Qca8081, or Qca8337) and that device has LTE/5G capability enabled, since all versions of these firmwares are vulnerable.
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 modem firmware updates addressing this vulnerability. Until the patch is available, monitor for unusual modem behavior and restrict physical proximity of untrusted devices to reduce attack surface.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33058 — 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-33058 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