CVE-2023-33049
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 Multi-Mode Call Processor due to UE failure because of heap leakage.
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 heap memory leakage vulnerability in the Multi-Mode Call Processor allows an attacker to cause a transient Denial of Service by exhausting heap memory through repeated operations. The vulnerability manifests as User Equipment (UE) failures due to the memory leak, leading to service disruption in the telecommunications network.
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 installed Qualcomm firmware productDetermine the exact Qualcomm firmware model running on the device (e.g., Fastconnect 6200, Fastconnect 7800, Qca6174a, Ar8035, or the 315 5g IoT modem). Check system information, modem firmware logs, or device specifications.Affected if The device runs any of the affected products: Qualcomm 315 5g IoT Modem, Ar8035, Fastconnect 6200/6700/6800/6900/7800, or Qca6174a firmware.
-
Verify Multi-Mode Call Processor is activeCheck whether the Multi-Mode Call Processor component is enabled and actively processing calls on the system. Inspect running processes or services related to call processing, telephony, or modem communication.Affected if The Multi-Mode Call Processor feature is currently enabled and handling call operations on the affected firmware.
-
Monitor heap memory usage patternsObserve heap memory allocation over time. Look for continuous growth in memory consumption that does not get released, particularly in call processor related processes. Compare memory usage before, during, and after call operations.Affected if Heap memory continuously increases with repeated call processing operations and does not return to baseline levels, indicating a memory leak.
-
Check for UE/service failure eventsReview system logs, modem logs, or network service status for user equipment failures, call drops, or service disruptions that correlate with prolonged or repeated call processing activity.Affected if UE failures or service disruptions occur after sustained or repeated call processing operations, with no other identifiable cause.
-
Confirm firmware version is unpatchedSince all versions of the affected firmware are vulnerable, verify that vendor patches for CVE-2023-33049 have not been applied. Check with the Qualcomm or device vendor for patch availability and installation status.Affected if The installed firmware has not received the CVE-2023-33049 security update from the vendor.
A system is affected if it runs any of the listed Qualcomm firmware products with the Multi-Mode Call Processor enabled, and exhibits heap memory exhaustion or service failures during call processing operations.
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 patches for the affected call processor software. Implement memory usage monitoring and alerting to detect heap leakage conditions before they cause service failure. Consider implementing resource limits and automatic recovery mechanisms.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33049 — 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-33049 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