CVE-2022-33211
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 improper check while calculating size of serialized CoAP message
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 confidenceThis is a memory corruption vulnerability in modem firmware where improper bounds checking occurs during size calculation for serialized CoAP (Constrained Application Protocol) messages. This likely results in a buffer overflow or underflow condition that could allow an attacker to overwrite memory and potentially achieve remote code execution.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the modem or baseband processor modelCheck system information, firmware details, or hardware specs for Qualcomm MDM8207, MDM9205, MDM9206, MDM9207, QCA4004, QTS110, or Snapdragon Wear 1100/1200 components. On Linux, this may appear in dmesg, /proc/cpuinfo, or vendor-specific diagnostic interfaces.Affected if The device uses any of the listed Qualcomm firmware products (all versions are affected)
-
Determine the firmware versionQuery the modem firmware version through AT commands (e.g., ATI, AT+CGMR), vendor diagnostic tools, or by inspecting the baseband firmware image file if accessible.Affected if The installed firmware version falls within the affected product lines (all versions of Mdm8207, Mdm9205, Mdm9206, Mdm9207, Qca4004, Qts110, Snapdragon Wear 1100, or Snapdragon Wear 1200)
-
Check if CoAP protocol is enabledReview the modem or IoT device configuration to determine if Constrained Application Protocol (CoAP) is actively enabled or configured. This may be found in network settings, service configurations, or application logs.Affected if CoAP protocol is enabled on the device, as this is the vulnerable feature where improper bounds checking occurs during message size calculation
-
Inspect network traffic for CoAP messagesUse network capture tools (tcpdump, Wireshark) to monitor outbound or inbound traffic on UDP port 5683 (default CoAP port) or custom CoAP ports. Analyze packet sizes and patterns.Affected if The device is transmitting or receiving CoAP messages, as malicious CoAP messages are the attack vector for this vulnerability
The environment is affected if it runs any version of the listed Qualcomm modem/firmware products with CoAP protocol enabled, as all versions of these products contain the vulnerability in CoAP message handling.
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 patch for the modem/baseband processor; if unavailable, implement network-level filtering of malicious CoAP messages at the network edge as a temporary mitigation.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33211 — 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-33211 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