CVE-2022-25733
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 · uneditedDenial of service in modem due to null pointer dereference while processing DNS 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 confidenceA null pointer dereference vulnerability exists in modem firmware when processing DNS packets. When the modem receives and attempts to process incoming DNS packets, a lack of proper null pointer validation causes the device to crash, resulting in denial of service.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 firmware versionQuery the device or modem for its firmware version using vendor-specific commands (such as AT command interfaces for Qualcomm modems, or check system logs that report modem firmware information). Compare the detected version against the affected product list (Ar8031, Csra6620, Csra6640, Mdm8207, Mdm9205, Mdm9206, Mdm9207, Mdm9607).Affected if The modem firmware matches any of the listed affected products and versions.
-
Confirm DNS packet processing is enabledExamine the modem or host configuration to determine whether DNS packet handling is actively enabled. This may be exposed through modem AT command queries, configuration files, or network settings that control DNS traffic routing to the modem.Affected if DNS packet processing is enabled on the affected modem firmware, making it susceptible to the null pointer dereference when malformed DNS packets arrive.
-
Inspect modem crash logs or reboot eventsReview system logs, modem diagnostic logs, or kernel messages for evidence of unexpected modem restarts, crashes, or null pointer dereference errors that coincide with DNS traffic processing.Affected if The device has experienced modem crashes or unexpected reboots linked to DNS packet handling, indicating possible exploitation of this vulnerability.
-
Verify network exposure of DNS to modemDetermine whether the modem's DNS processing path is reachable from the network. Check if the device accepts incoming DNS packets on interfaces connected to the vulnerable modem firmware.Affected if The modem's DNS interface is network-accessible and the affected firmware is in use, the device can be triggered by malicious DNS packets.
A user is affected if their device contains any of the listed Qualcomm modem firmware versions (Ar8031, Csra6620, Csra6640, Mdm8207, Mdm9205, Mdm9206, Mdm9207, Mdm9607) with DNS packet processing functionality enabled and network exposure to DNS traffic.
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 when available. If no update exists, implement network-level filtering of malformed DNS packets as a temporary mitigation until firmware can be patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25733 — 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-25733 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