CVE-2022-25745
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 · uneditedMemory corruption in modem due to improper input validation while handling the incoming CoAP message
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 confidenceMemory corruption vulnerability in modem firmware stemming from improper input validation when parsing incoming CoAP (Constrained Application Protocol) messages. The lack of proper bounds checking or validation allows malformed CoAP packets to trigger memory corruption, potentially leading to remote code execution or 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 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 or firmware modelQuery the device for its modem or firmware identifier using commands such as 'AT+CGMM' for AT-command capable modems, or check system information files under /proc or /sys that expose the modem model (e.g., /proc/device-tree/model, /sys/class/net/*/device/uevent, or vendor-specific diagnostic interfaces).Affected if The modem model matches Mdm9205, Qca4004, Qts110, Snapdragon Wear 1300, or Wcd9306.
-
Determine if CoAP service is enabledExamine the firmware or operating system configuration for CoAP server or client settings. This may include checking configuration files in /etc, /opt, or vendor-specific directories; querying the modem via AT commands like 'AT+QCOAP?' (if supported); or reviewing the application manifest that defines enabled network services.Affected if CoAP protocol handling is enabled or available on the device.
-
Verify CoAP listener presence on the networkScan for open CoAP ports using 'nmap -sU -p 5683 <target>' or perform a socket inspection with 'netstat -uan | grep 5683' or 'ss -uan | grep 5683' to check if the device is listening on the standard CoAP UDP port 5683.Affected if The device has a CoAP service listening on UDP port 5683.
-
Inspect CoAP traffic for anomaliesCapture network packets on the interface connected to the modem using 'tcpdump -i <interface> udp port 5683 -c 10' or similar packet capture tools, then analyze the captured CoAP messages for malformed headers, unexpected payload sizes, or invalid option values.Affected if The device processes incoming CoAP packets from untrusted network sources.
The environment is affected if it contains any of the listed Qualcomm modem firmware models (Mdm9205, Qca4004, Qts110, Snapdragon Wear 1300, or Wcd9306) and has CoAP protocol enabled or exposed to network 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 dataUpdate modem firmware to vendor-provided patch addressing CoAP input validation. If no patch available, consider network segmentation to limit modem exposure and monitor for anomalous CoAP traffic.
- Consultation6.0 h
- Implementation16.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 $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25745 — 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-25745 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