CVE-2022-33296
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 due to integer overflow to buffer overflow in Modem while parsing Traffic Channel Neighbor List Update 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 · high confidenceA memory corruption vulnerability exists in the modem component where an integer overflow occurs during parsing of the Traffic Channel Neighbor List Update message. This integer overflow leads to a buffer overflow, allowing memory corruption. The vulnerability is exploitable and rated high severity due to the potential for 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
- 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 the modem hardware modelReview system documentation, hardware inventory, or use diagnostic commands (such as 'at+qversion' or vendor-specific modem status commands) to determine the exact Qualcomm modem chip or firmware product name in useAffected if The identified modem model matches any of: Qualcomm 315 5g Iot Modem, Apq8017, Aqt1000, Ar8035, Csrb31024, Wcn3998, Qca6390, or Wcn685x 5
-
Confirm the firmware versionExecute the appropriate firmware version query command for your modem (commonly 'at+cgmr', 'at+qfirmware', or vendor-specific diagnostic interfaces) and record the reported firmware build numberAffected if Any version is reported, since all versions of the listed firmware products are affected according to the advisory
-
Verify the modem component is activeCheck modem status via system logs, diagnostic interfaces, or network configuration to confirm the modem is powered on and processing cellular trafficAffected if The modem component is operational and capable of receiving Traffic Channel Neighbor List Update messages
-
Determine network exposureReview network topology and access controls to assess whether untrusted adjacent attackers could send malicious Traffic Channel messages to the modemAffected if The modem has direct network adjacency to untrusted devices or is accessible to adjacent attack vectors without proper segmentation
If your environment contains any of the listed Qualcomm modem firmware products (315 5g Iot, Apq8017, Aqt1000, Ar8035, Csrb31024, Wcn3998, Qca6390, or Wcn685x 5), you are affected since all versions are vulnerable to this integer overflow during Traffic Channel Neighbor List Update message parsing.
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.
dbcve · scopedApply vendor-provided firmware/security updates for the affected modem component. If no patch is available, implement network segmentation to limit exposure to adjacent attackers and monitor for indicators of exploitation targeting this vector.
Firmware update from OEM containing Qualcomm security patch (contact device vendor for specific version)
- Contact your device/OEM manufacturer to obtain firmware updates addressing CVE-2022-33296
- Verify with the OEM that the update includes the fix for the integer overflow vulnerability in Modem Traffic Channel Neighbor List Update message parsing
- Apply the OEM-provided firmware update following the manufacturer's recommended procedures
- After update, confirm the modem firmware version matches the patched release
Generated from the published advisory — verify against the referenced sources before acting.
- 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-33296 — 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-33296 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