CVE-2022-25731
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 due to buffer over-read while processing packets from DNS server
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 buffer over-read vulnerability in modem firmware allows information disclosure when processing packets from a DNS server. The vulnerability occurs when the modem reads beyond the allocated buffer boundaries while parsing DNS responses, potentially exposing sensitive memory contents to an attacker.
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 modelCheck your device inventory, network topology, or hardware specifications for Qualcomm modem chips. Look for Mdm9205, Mdm9206, Mdm9207, Mdm8207, Qca4004, Qca4010, Qts110, or Snapdragon Wear 1100 modules.Affected if Any of these specific Qualcomm modem models are present in your environment
-
Verify the firmware versionAccess the modem firmware management interface or check the firmware version string reported by the device. Compare against the affected list - note that all versions are affected.Affected if The installed firmware version corresponds to any of the listed affected products
-
Confirm DNS processing is enabledCheck the modem or device configuration for DNS client functionality. Look for DNS resolution settings, DNS server configuration, or network interface settings that enable DNS response handling.Affected if DNS client or DNS response processing is enabled on the affected modem
-
Assess network exposure to DNS trafficReview network configuration to determine if the modem processes DNS responses from external or untrusted DNS servers. Check firewall rules and network segmentation around the modem device.Affected if The modem can receive DNS responses from network sources that are not explicitly trusted
If your environment contains any of the listed Qualcomm modem models (Mdm9205, Mdm9206, Mdm9207, Mdm8207, Qca4004, Qca4010, Qts110, Snapdragon Wear 1100) with DNS processing enabled, 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 dataApply vendor-supplied firmware patches when available. If no patch exists, implement network segmentation to isolate vulnerable modem devices and restrict DNS traffic to trusted servers.
- 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-25731 — 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-25731 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