CVE-2022-33295
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 · uneditedInformation disclosure in Modem due to buffer over-read while parsing the wms message received given the buffer and its length.
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 over-read vulnerability in the modem component allows information disclosure during parsing of WMS (Wireless Messaging Service) messages. The vulnerability occurs when the modem processes a received wms message without proper bounds checking on the buffer and its length, causing the over-read to leak sensitive memory contents.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 modelConsult device hardware documentation, system information utilities, or modem AT commands (such as AT+CGMM or AT+GMM) to determine the exact modem chipset modelAffected if The modem model matches any of the following: Mdm8207, Mdm9205, Mdm9206, Mdm9207, Qca4004, Qts110, Snapdragon Wear 1100, or Snapdragon Wear 1200
-
Check if WMS messaging is enabledExamine the device configuration or modem settings for WMS (Wireless Messaging Service) support. This may be accessible through carrier settings, messaging app configuration, or modem AT commands related to WMS (such as AT+UWFS or similar vendor-specific commands)Affected if WMS functionality is active and the modem processes incoming WMS messages
-
Verify firmware version of the affected modemQuery the modem firmware version using appropriate AT commands (for example, AT+CGMR or AT+VER) or through device system information if accessibleAffected if The firmware version corresponds to any version of the affected Qualcomm products listed
A device is affected if it contains any of the listed Qualcomm modem chipsets (Mdm8207, Mdm9205, Mdm9206, Mdm9207, Qca4004, Qts110, Snapdragon Wear 1100, or Snapdragon Wear 1200) and has WMS messaging functionality enabled, as all firmware versions of these products contain the vulnerability.
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 modem/baseband processor when available. Until a patch is released, monitor network traffic for malformed wms messages and restrict device access to trusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33295 — 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-33295 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