Mdm8207 FirmwareOperating system · Qualcomm

CVE-2022-33228

HIGH · 7.5 CVSS v3.1 Published 2023-04-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
Information disclosure sue to buffer over-read in modem while processing ipv6 packet with hop-by-hop or destination option in header.

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 buffer over-read vulnerability in the modem component allows an unauthenticated remote attacker to disclose sensitive memory contents by sending specially crafted IPv6 packets containing hop-by-hop or destination options in the header. This occurs during the parsing of IPv6 extension headers in the modem's network stack.

MitigationApply vendor-provided firmware patches for the affected modem devices. As an interim measure, consider filtering or blocking IPv6 packets with hop-by-hop or destination options at network perimeter devices if the modem cannot be immediately patched.

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
Mdm8207 FirmwareOperating system
Affected:all versions
Mdm9205 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9207 FirmwareOperating system
Affected:all versions
Qca4004 FirmwareOperating system
Affected:all versions
Qts110 FirmwareOperating system
Affected:all versions
Snapdragon Wear 1100 FirmwareOperating system
Affected:all versions
Snapdragon Wear 1200 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
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 checks

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

  1. Identify the modem or device model
    Check the device documentation, label, or system information to determine the exact model number (e.g., Mdm9207, Qca4004, Snapdragon Wear 1100)
    Affected if The model matches one of the affected products: Mdm8207, Mdm9205, Mdm9206, Mdm9207, Qca4004, Qts110, Snapdragon Wear 1100, or Snapdragon Wear 1200
  2. Confirm firmware vendor and lineage
    Check if the device uses Qualcomm modem firmware by reviewing firmware version strings, boot logs, or modem diagnostic information
    Affected if The device runs Qualcomm-based modem firmware for any of the affected chipsets
  3. Determine IPv6 protocol exposure
    Review network configuration to see if IPv6 is enabled on the modem interface, and check if the device is directly accessible via IPv6 (public IPv6 address, direct cellular connection)
    Affected if IPv6 is enabled and the modem interface can receive directly addressed IPv6 traffic from untrusted sources
  4. Assess network perimeter controls
    Check whether upstream network devices, firewalls, or gateways are filtering or blocking inbound IPv6 packets containing hop-by-hop or destination extension options
    Affected if IPv6 traffic with extension headers is permitted through to the modem without filtering
  5. Review modem logs for crash or memory read anomalies
    Examine modem crash dumps, AT command logs, or diagnostic outputs for any unexpected buffer over-read errors or memory disclosure indications
    Affected if Any logs show symptoms of buffer over-read or unexpected memory access during IPv6 header parsing

A defender is affected if their device uses one of the listed Qualcomm modem products and has IPv6 connectivity that allows specially crafted packets with extension headers to reach the modem's network stack.

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-provided firmware patches for the affected modem devices. As an interim measure, consider filtering or blocking IPv6 packets with hop-by-hop or destination options at network perimeter devices if the modem cannot be immediately patched.

Fix this in Mdm8207 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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