CVE-2022-25737
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 missing NULL check while reading packets received from local network
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 caused by a missing NULL pointer check when processing packets received from the local network. This allows attackers to potentially read sensitive data from memory when the modem processes incoming network packets.
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/hardware modelCheck the device label, FCC ID, or system information to determine if the hardware uses a Qualcomm modem from the affected list (Mdm8207, Mdm9205, Mdm9206, Mdm9207, Qca4004, Qts110, Snapdragon Wear 1100, or Snapdragon Wear 1200)Affected if The device contains any of the listed Qualcomm modem chipsets or wearable platforms
-
Confirm firmware versionAccess the modem firmware version through AT command (e.g., AT+CGMR or ATI), device management interface, or boot logs, and verify it matches one of the affected product linesAffected if The device runs firmware on any of the listed Qualcomm platforms (all versions are affected)
-
Check network exposureDetermine if the modem's network interface is directly accessible from untrusted network segments by reviewing network topology, firewall rules, and interface configurationsAffected if The modem processing incoming packets is reachable from local or wide area networks without network segmentation
You are affected if your device or system contains any of the listed Qualcomm modem or wearable firmware products (Mdm8207, Mdm9205, Mdm9206, Mdm9207, Qca4004, Qts110, Snapdragon Wear 1100, or Snapdragon Wear 1200), regardless of version, and the modem is exposed to network packet processing.
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 that add proper NULL pointer validation before reading packet data. If no patch available, consider network segmentation to limit exposure of the vulnerable modem.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25737 — 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-25737 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