Apq8009w FirmwareOperating system · Qualcomm

CVE-2021-30300

HIGH · 7.5 CVSS v3.1 Published 2022-01-13
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
Possible denial of service due to incorrectly decoding hex data for the SIB2 OTA message and assigning a garbage value to choice when processing the SRS configuration in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables

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 · high confidence

A denial of service vulnerability exists in Qualcomm Snapdragon baseband firmware where incorrectly decoded hex data in the SIB2 OTA (System Information Block 2 Over-The-Air) message causes a garbage value to be assigned to a choice variable during SRS (Sounding Reference Signal) configuration processing. This memory corruption or invalid state assignment can cause the device to crash or become unresponsive.

MitigationApply the Qualcomm firmware/security patch (CVE-2021-30300) from the device OEM. Users should check for and apply available firmware updates for affected Snapdragon devices.

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
Apq8009w FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Csrb31024 FirmwareOperating system
Affected:all versions
Fsm10055 FirmwareOperating system
Affected:all versions
Fsm10056 FirmwareOperating system
Affected:all versions
Mdm8207 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 device chipset model
    Check the device specifications or use AT commands (like 'AT+GMR' or 'AT+CGMM' for Qualcomm modems) to query the modem chipset/model number
    Affected if The chipset matches Apq8009w, Apq8017, Apq8096au, Ar8035, Csrb31024, Fsm10055, Fsm10056, or Mdm8207
  2. Confirm firmware version
    Query the baseband firmware version using vendor-specific AT commands (such as 'AT+QLFVER' or through the device's engineering mode), or check the modem firmware information in the device's about/settings pages
    Affected if Any firmware version is installed on an affected chipset - all versions are vulnerable
  3. Verify cellular network connectivity
    The vulnerability triggers during SIB2 OTA message processing during normal cellular operation. Check if the device has active LTE/5G connectivity by examining network status
    Affected if Device has cellular capability and connects to a mobile network - the flaw activates when processing SIB2 messages from the network
  4. Check for OEM firmware updates
    Contact the device OEM or check the manufacturer support website for available firmware/security patches for this specific device model
    Affected if No firmware update addressing CVE-2021-30300 has been applied by the OEM

If the device uses any of the affected Qualcomm chipset models (Apq8009w, Apq8017, Apq8096au, Ar8035, Csrb31024, Fsm10055, Fsm10056, Mdm8207) and processes cellular network signals without the corresponding security patch, the device is vulnerable to denial of service via malformed SIB2 OTA messages.

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 the Qualcomm firmware/security patch (CVE-2021-30300) from the device OEM. Users should check for and apply available firmware updates for affected Snapdragon devices.

Fix this in Apq8009w Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-30300 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-30300 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