CVE-2025-23417
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 · uneditedA denial of service vulnerability exists in the Modbus RTU over TCP functionality of Socomec DIRIS Digiware M-70 1.6.9. A specially crafted network packet can lead to denial of service. An attacker can send an unauthenticated packet to trigger this vulnerability.
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 denial of service vulnerability exists in the Modbus RTU over TCP functionality of Socomec DIRIS Digiware M-70 power monitoring device version 1.6.9. An unauthenticated attacker can send a specially crafted network packet to trigger this vulnerability, causing the device to become unavailable.
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 data= 1.6.9CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Socomec DIRIS Digiware M-70 device on the networkScan the network for devices responding to Modbus TCP (port 502) or with product-specific HTTP/web interfaces. Check device hostname, MAC OUI (Socomec), or SNMP sysDescr for 'DIRIS Digiware M-70' or 'Socomec' identifiers.Affected if The device is a Socomec DIRIS Digiware M-70 power monitoring unit.
-
Determine the installed firmware versionAccess the device web interface (if available) and navigate to System Info, About, or Firmware version page. Alternatively, query the device via Modbus register (consult device documentation for version register) or SNMP OID.Affected if The firmware version is exactly 1.6.9.
-
Verify Modbus RTU over TCP is enabledCheck device configuration via web interface or Modbus setup menu for 'Modbus RTU over TCP' or 'Modbus TCP' enable status. Confirm the service is active and listening on the network.Affected if Modbus RTU over TCP functionality is enabled and the service is running.
-
Assess network accessibility of Modbus servicePerform a port scan targeting the device IP address on port 502 (standard Modbus TCP). Verify if the device Modbus TCP interface is directly reachable from untrusted networks or the internet.Affected if The device Modbus TCP port (502) is exposed to untrusted or external networks without firewall protection.
You are affected if the device is a Socomec DIRIS Digiware M-70 running firmware version 1.6.9 with Modbus RTU over TCP enabled and accessible over the network.
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 dataRestrict network access to the device's Modbus TCP ports using firewalls or network segmentation. If available, apply vendor-supplied firmware updates. Monitor for DoS conditions on affected devices.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23417 — 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-2025-23417 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