CVE-2022-25726
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 data due to array out of bound access while handling the incoming DNS response packet
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 high-severity information disclosure vulnerability exists in modem firmware where an array out-of-bounds access occurs during parsing of incoming DNS response packets. This improper bounds checking allows attackers to read adjacent memory contents, potentially exposing sensitive modem data.
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 modem chipset modelCheck device documentation, hardware specs, or use AT commands (e.g., AT+CGMM or AT+CGMI) to query the modem modelAffected if The modem model matches Qualcomm Mdm9205, Mdm9206, Mdm9207, Wcn685x 1, Wcn785x 1, Mdm8207, Qca4004, or Qts110
-
Verify firmware versionQuery the modem firmware version using AT commands such as AT+CGMR or ATI. Compare the returned version against the affected product listAffected if The firmware version corresponds to any of the listed affected products (all versions are vulnerable)
-
Confirm DNS processing is activeCheck modem configuration for DNS settings using AT+CNDSN or similar DNS-related AT commands. Verify the modem is configured to process DNS responsesAffected if DNS response parsing is enabled on the modem, which is the default operational mode
-
Assess network exposure of modem interfaceReview network architecture and firewall rules to determine if the modem management interface or data plane is accessible from untrusted networksAffected if The modem is reachable from network segments that could contain malicious DNS responses
If your environment contains any of the listed Qualcomm modem models (Mdm9205, Mdm9206, Mdm9207, Wcn685x 1, Wcn785x 1, Mdm8207, Qca4004, Qts110) and the modem processes DNS traffic, you are affected since all versions of these products are vulnerable.
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-provided firmware patches for the modem. If no patch is available, consider network segmentation to limit modem exposure and implement additional DNS filtering at the network perimeter.
- 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-25726 — 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-25726 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