CVE-2022-33277
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 modem due to buffer copy without checking size of input while receiving WMI 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 confidenceA buffer overflow vulnerability exists in the modem firmware where incoming WMI (Wireless Multimedia Extensions) commands are processed without validating input size before copying data into a fixed-length buffer. This can lead to memory corruption and potentially allow code execution in the modem context.
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 Qualcomm modem hardwareExamine system hardware inventory using commands such as 'lspci', 'lsusb', 'dmidecode', or check Device Manager on Windows. Look for any of the following modem identifiers: Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, or Csrb31024.Affected if Any of the listed Qualcomm modem components are present in the system
-
Retrieve modem firmware versionQuery the modem firmware version through vendor-specific interfaces. On Linux, this may involve AT commands via serial/USB (e.g., 'echo ATI1 > /dev/ttyUSB0'), or checking firmware files in /lib/firmware, /etc/firmware, or /boot. On Windows, use device properties in Device Manager under the modem device details.Affected if The retrieved firmware version matches any of the affected products (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024) regardless of version number
-
Verify WMI command processing is activeConfirm that the modem's WMI (Wireless Multimedia Extensions) interface is enabled and actively processing commands. This typically cannot be directly inspected from the host system as it operates within the modem firmware context. Review system logs or modem diagnostic outputs for WMI-related activity if available.Affected if The modem is operational and processing wireless multimedia commands, which is the default state for an active modem
If the system contains any of the listed Qualcomm modem firmware components (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, or Csrb31024) and the modem is actively processing commands, the environment is affected since all versions of these firmwares are vulnerable.
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-supplied firmware updates for the affected modem components. This is a baseband/modem firmware issue that cannot be mitigated through network-level controls or software patches on the host system.
- Consultation8.0 h
- Implementation4.0 h
- Testing16.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 $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33277 — 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-2022-33277 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