CVE-2022-33229
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 due to buffer over-read in Modem while using static array to process IPv4 packets.
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 confidenceBuffer over-read vulnerability in modem firmware when processing IPv4 packets using a static array, allowing disclosure of memory contents beyond array bounds.
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 hardware modelLocate and inspect the physical modem hardware or query the device management interface for the modem model number (e.g., Ar8031, Csra6620, Csra6640, Mdm8207, Mdm9205, Mdm9206, Mdm9207, Mdm9607)Affected if The modem model matches any of the following: Ar8031, Csra6620, Csra6640, Mdm8207, Mdm9205, Mdm9206, Mdm9207, or Mdm9607
-
Retrieve the modem firmware versionQuery the modem via AT commands (e.g., AT+CGMR) or through the device's firmware management interface to obtain the installed firmware versionAffected if Any firmware version is installed on the affected modem models (all versions are vulnerable)
-
Verify IPv4 packet processing is enabledCheck the modem or host device configuration for IPv4 protocol support and packet processing settings; review network configuration files or management interfaces that control IPv4 handlingAffected if IPv4 packet processing is enabled on the modem (the vulnerability triggers when processing IPv4 packets)
-
Confirm IPv4 traffic flows through the modemMonitor network traffic logs or packet captures to verify IPv4 packets are being processed by the modem componentAffected if IPv4 packets are being processed by the vulnerable modem (this exposes the attack surface)
If your environment contains any of the listed Qualcomm modem models (Ar8031, Csra6620, Csra6640, Mdm8207, Mdm9205, Mdm9206, Mdm9207, Mdm9607) with IPv4 packet processing enabled and active, you are affected by this 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 dataUpdate modem firmware to vendor-patched version; if patch unavailable, implement network segmentation to limit attack surface against the modem component.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33229 — 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-33229 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