CVE-2023-22388
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 Multi-mode Call Processor while processing bit mask API.
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 confidenceThis is a memory corruption vulnerability in a Multi-mode Call Processor component that occurs during processing of a bit mask API. The critical CVSS score of 9.8 indicates this likely allows remote unauthenticated attackers to execute arbitrary code or cause denial of service via specially crafted inputs to the bit mask processing function.
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 your modem or device modelCheck the product label, device inventory, or system documentation for the exact model number (e.g., Qualcomm 315 5G IoT Modem, 9205 LTE Modem, APQ8017, etc.)Affected if The model matches any of the affected products listed in the CVE (315 5G, 9205, 9206, 9207, APQ8017, APQ8037, AQT1000, AR8035)
-
Determine the firmware versionAccess the device management interface or use AT commands (e.g., AT+CGMR or ATI) to query the installed Qualcomm firmware versionAffected if The firmware version cannot be patched (all versions of affected products are vulnerable)
-
Verify Multi-mode Call Processor is activeCheck device diagnostics, module status, or network configuration to confirm the call processor component is enabled and runningAffected if The Multi-mode Call Processor component is present and operational on the device
-
Assess network exposureReview firewall rules, port exposures, and network segmentation around the modem component to determine if the call processor API is accessible from network interfacesAffected if The bit mask API endpoint of the call processor is reachable from untrusted networks or the internet
If your device uses any of the listed Qualcomm firmware products (315 5G, 9205, 9206, 9207, APQ8017, APQ8037, AQT1000, AR8035) with the Multi-mode Call Processor enabled and network-accessible, your environment is affected by this 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 patches immediately as they become available. If no patch exists, consider network segmentation to restrict access to the call processor component and monitor for exploitation indicators.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22388 — 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-22388 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