CVE-2023-33025
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 · uneditedMemory corruption in Data Modem when a non-standard SDP body, during a VOLTE call.
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 confidenceMemory corruption vulnerability in the Data Modem component that triggers when processing a non-standard (malformed) SDP body during an active VoLTE call. The vulnerability allows memory corruption that could lead to remote code execution or service disruption.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Qualcomm modem firmware modelCheck the device's modem firmware information through AT commands (e.g., AT+CGMR or AT+GMR), system logs, or vendor documentation to determine the chipset model (Ar8035, Fastconnect 6700, Fastconnect 6900, Qca8081, Qca8337, Qcm4490, Qcn6024, or Qcn9024)Affected if The modem firmware model matches any of the affected chipsets: Ar8035, Fastconnect 6700, Fastconnect 6900, Qca8081, Qca8337, Qcm4490, Qcn6024, or Qcn9024
-
Verify the Data Modem component is in useConfirm the device utilizes a Data Modem component for cellular connectivity by checking the system configuration, modem status, or network interface settingsAffected if The device uses a Data Modem for cellular communication and the firmware model matches the affected list
-
Determine if VoLTE is enabledCheck the device's VoLTE configuration through modem settings, carrier settings, or by querying the modem (e.g., AT+CFUN? or through QMI/NAS interface) for VoLTE capability statusAffected if VoLTE (Voice over LTE) is enabled and active on the device; the vulnerability triggers specifically during VoLTE call processing
-
Check for active or recent VoLTE callsReview call logs, modem event logs, or use diagnostic commands to identify if VoLTE calls have been made or received on the deviceAffected if VoLTE calls have been processed by the device; the vulnerability triggers when processing SDP bodies during active VoLTE sessions
The environment is affected if the device runs any of the listed Qualcomm firmware models (Ar8035, Fastconnect 6700/6900, Qca8081, Qca8337, Qcm4490, Qcn6024, Qcn9024) with an active Data Modem component and VoLTE enabled or used.
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 firmware updates for affected data modem components. Until patched, limit exposure by avoiding untrusted VoLTE call sources and monitoring for anomalous modem behavior.
- Consultation8.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 $6,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33025 — 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-33025 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