dbcve.org
Snapdragon 855\+\/860 Mobile Platform \(sm8150 Ac\) FirmwareOperating system · Qualcomm

CVE-2024-23352

HIGH · 7.5 CVSS v3.1 Published 2024-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Transient DOS when NAS receives ODAC criteria of length 1 and type 1 in registration accept OTA.

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 confidence

This is a denial of service vulnerability in Network Access Server (NAS) equipment where processing of specific ODAC (Object Data Access Criteria) parameters during OTA (Over-The-Air) registration accept messages causes a transient crash or hang. The vulnerability is triggered by receiving ODAC criteria with length=1 and type=1, indicating a lack of proper bounds checking or error handling for this specific parameter combination.

MitigationApply vendor firmware/software updates to NAS equipment that address proper validation and error handling for ODAC criteria parameters. Until patched, monitor for service interruptions and implement network-level filtering if the vendor provides specific signatures.

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 data
Snapdragon 855\+\/860 Mobile Platform \(sm8150 Ac\) FirmwareOperating system
Affected:all versions
Wsa8845h FirmwareOperating system
Affected:all versions
Wsa8845 FirmwareOperating system
Affected:all versions
Wsa8840 FirmwareOperating system
Affected:all versions
Wsa8835 FirmwareOperating system
Affected:all versions
Wsa8832 FirmwareOperating system
Affected:all versions
Wsa8830 FirmwareOperating system
Affected:all versions
Wsa8815 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the firmware version on the device
    Check the device firmware version via system info, bootloader, or modem diagnostic interface. For Qualcomm devices, this can often be retrieved via AT commands (AT+CGMR or AT+GMR), through the /proc/version or /proc/cpuinfo files on embedded Linux systems, or via vendor-specific diagnostic tools.
    Affected if The device runs any firmware version on the listed affected chipsets (sm8150 Ac, Wsa8845h, Wsa8845, Wsa8840, Wsa8835, Wsa8832, Wsa8830, Wsa8815).
  2. Determine if OTA registration processing is enabled
    Check device configuration or network settings to see if Over-The-Air (OTA) registration accept message processing is active. This is typically found in NAS (Network Access Server) configuration, modem settings, or radio protocol stack configuration.
    Affected if The device processes OTA registration accept messages. If OTA registration is disabled or not used, the vulnerability is not triggerable.
  3. Inspect ODAC parameter handling in network logs
    Monitor or capture network traffic during OTA registration. Look for ODAC (Object Data Access Criteria) parameters in registration accept messages. Use protocol analyzers or vendor diagnostic tools that can decode NAS/RRC messages containing ODAC criteria.
    Affected if The device receives ODAC criteria with length=1 and type=1 in OTA registration accept messages. This specific combination triggers the lack of bounds checking.
  4. Check for service interruptions after OTA registration
    Monitor device logs (modem logs, kernel logs, system logs) around the time of OTA registration for crash reports, hang events, or unexpected resets. Look for patterns indicating NAS processing failures.
    Affected if The device experiences transient crashes or hangs immediately after processing OTA registration accept messages containing the specific ODAC parameters.

The device is affected if it runs firmware on any of the listed Qualcomm chipsets AND processes OTA registration accept messages with ODAC criteria where length=1 and type=1.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware/software updates to NAS equipment that address proper validation and error handling for ODAC criteria parameters. Until patched, monitor for service interruptions and implement network-level filtering if the vendor provides specific signatures.

Fix this in Snapdragon 855\+\/860 Mobile Platform \(sm8150 Ac\) Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23352 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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