CVE-2023-24852
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 Core due to secure memory access by user while loading modem image.
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 Core (likely baseband/modem processor) allows a local user to improperly access secure memory during the modem image loading process, potentially leading to code execution or privilege escalation within the secure domain.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 affected Qualcomm modem hardwareInventory network devices, IoT equipment, or embedded systems for Qualcomm 315 5G, 9205 LTE, Aqt1000, Ar8031, Ar8035, C-V2X 9150, Csr8811, or Csra6620 modems or modules. Check device labels, SNMP inventory, or hardware specifications.Affected if Any of these specific Qualcomm modem models or chipsets are present in the environment
-
Check modem firmware versionAccess the modem management interface (AT commands, debug serial, OEM management portal) and query the firmware version using vendor-specific commands (e.g., AT+CGMR, ATI, or platform-specific diagnostic tools).Affected if Firmware version cannot be determined or is confirmed to be any version of the listed products
-
Verify modem image loading interface exposureReview network access controls, debug port exposure, and management interface configurations. Check if modem firmware update/loading interfaces (JTAG, debug serial, OEM diagnostic ports, or network-based firmware update services) are accessible to local users or network attackers.Affected if Modem image loading or firmware update mechanisms are exposed to untrusted local users or network access
-
Check for unauthorized firmware modificationsCompare current modem firmware hash or version against known-good baseline from vendor documentation. Look for unexpected firmware images, unauthorized flashing attempts in system logs, or unknown firmware signatures.Affected if Firmware hash differs from vendor baseline or unauthorized modification indicators are present
-
Audit user access to modem subsystemsReview logs and access controls for modem core/baseband processor interfaces. Check if local user accounts or debugging tools have access to secure memory regions or modem image loading functions.Affected if Local users have elevated access to modem core functions or secure memory regions
If any Qualcomm 315/9205-series or listed modem firmware is present and the modem image loading mechanism is accessible to local users, the environment is likely 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-provided firmware/security updates for affected devices. Until patch is available, restrict user access to modem image loading mechanisms and monitor for unauthorized firmware modifications.
- Consultation4.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 $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24852 — 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-24852 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