Ar8035 FirmwareOperating system · Qualcomm

CVE-2022-33276

HIGH · 7.8 CVSS v3.1 Published 2023-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Memory corruption due to buffer copy without checking size of input in modem while receiving WMI_REQUEST_STATS_CMDID command.

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

A memory corruption vulnerability exists in the modem component where a WMI_REQUEST_STATS_CMDID command handler performs a buffer copy operation without validating the input size, leading to a buffer overflow and subsequent memory corruption. The flaw allows an attacker to potentially execute arbitrary code or cause denial of service by sending a specially crafted command with oversized data.

MitigationApply vendor-supplied firmware patches addressing the buffer overflow in the modem's WMI command handler. As an interim measure, restrict network access to the modem interface to reduce exposure to malicious command injection.

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
Ar8035 FirmwareOperating system
Affected:all versions
Ar9380 FirmwareOperating system
Affected:all versions
Csr8811 FirmwareOperating system
Affected:all versions
Ipq5010 FirmwareOperating system
Affected:all versions
Ipq5018 FirmwareOperating system
Affected:all versions
Ipq5028 FirmwareOperating system
Affected:all versions
Ipq6000 FirmwareOperating system
Affected:all versions
Ipq6010 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
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 checks

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

  1. Identify the Qualcomm modem component in use
    Examine system documentation, hardware specifications, or boot logs to determine if the device uses any of the following modem/Firmware components: Ar8035, Ar9380, Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, or Ipq6010
    Affected if The system uses any of the listed Qualcomm firmware components (Ar8035, Ar9380, Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010)
  2. Determine the firmware version
    Access the modem or baseband processor firmware version through vendor-specific diagnostic interfaces, AT command prompts (for cellular modems), or by inspecting firmware image metadata if accessible
    Affected if The firmware version matches any of the affected products listed (all versions of the listed firmware are affected)
  3. Verify WMI interface is enabled
    Check modem configuration settings or system logs for WMI (Wireless Management Interface) service status. Look for WMI_REQUEST_STATS_CMDID or similar WMI command handler functionality in the modem firmware documentation or debug interfaces
    Affected if WMI command handling is enabled and accessible on the modem component
  4. Assess network exposure of modem interface
    Review network configuration, firewall rules, and access control lists to determine if the modem management or WMI interface is reachable from network segments. Check for exposed management ports or APIs associated with the Qualcomm modem component
    Affected if The modem interface with WMI command handling is network-accessible beyond trusted boundaries

A system is affected if it contains any of the listed Qualcomm firmware components (Ar8035, Ar9380, Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6010) with WMI functionality enabled and accessible.

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-supplied firmware patches addressing the buffer overflow in the modem's WMI command handler. As an interim measure, restrict network access to the modem interface to reduce exposure to malicious command injection.

Fix this in Ar8035 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA8.0 h
80.0 hours of engineering $13,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-33276 — 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-2022-33276 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