CVE-2022-25730
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 improper check of IP type while processing DNS server query
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 confidenceInformation disclosure vulnerability in modem firmware where improper validation of IP address type (IPv4 vs IPv6) during DNS server query processing allows unauthorized access to sensitive information.
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 firmware modelAccess the device management interface or log into the modem via serial/SSH and run commands such as 'AT+CGMR', 'AT+GMR', or check /proc/version to retrieve the firmware model identifierAffected if The model matches Mdm8207, Mdm9205, Mdm9206, Mdm9207, Qca4004, Qca4010, Qts110, or Snapdragon Ar2 Gen 1 Platform
-
Verify DNS server query functionality is in useCheck the modem configuration for DNS server settings, typically found in network configuration files, web UI, or via AT commands like 'AT+DNSSERVER?' or 'AT+QDNS'Affected if DNS server query processing is enabled and accessible on the modem
-
Confirm the modem is exposed to network accessReview firewall rules, access control lists, and network segmentation to determine if the modem's DNS query interface is reachable from untrusted networksAffected if The modem DNS functionality is accessible from networks outside the trusted internal network
-
Check for IPv4/IPv6 DNS configurationExamine the modem's DNS settings to determine if both IPv4 and IPv6 DNS servers are configured, as the vulnerability involves improper validation between address typesAffected if Both IPv4 and IPv6 DNS configurations exist on the modem
A user is affected if their device runs any of the listed Qualcomm modem firmware products (Mdm8207, Mdm9205, Mdm9206, Mdm9207, Qca4004, Qca4010, Qts110, Snapdragon Ar2 Gen 1) with DNS server query processing enabled and accessible from their network environment.
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 update to the affected modem devices to patch the DNS processing logic; if no update is available, implement network segmentation to isolate the modem and limit exposure to untrusted networks.
- 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-25730 — 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-25730 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