dbcve.org
Diris M 70 FirmwareOperating system · Socomec

CVE-2025-54850

HIGH · 7.5 CVSS v3.1 Published 2025-12-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A denial of service vulnerability exists in the Modbus TCP and Modbus RTU over TCP functionality of Socomec DIRIS Digiware M-70 1.6.9. A specially crafted series of network requests can lead to a denial of service. An attacker can send a sequence of unauthenticated packets to trigger this vulnerability.An attacker can trigger this denial-of-service condition by sending a sequence of Modbus RTU over TCP messages to port 503 using the Write Single Register function code (6). The attack sequence begins with a message to register 58112 with a value of 1000, indicating that a configuration change will follow. Next, a message is sent to register 29440 with a value corresponding to the new Modbus address to be configured. Finally, a message to register 57856 with a value of 161 commits the configuration change. After this configuration change, the device will be in a denial-of-service state.

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 · high confidence

A denial of service vulnerability exists in the Modbus TCP and Modbus RTU over TCP functionality of Socomec DIRIS Digiware M-70 v1.6.9. An unauthenticated attacker can trigger the DoS condition by sending a specific three-message sequence to port 503 using Write Single Register (function code 6): writing 1000 to register 58112, then a new Modbus address to register 29440, then 161 to register 57856 to commit the configuration change. This configuration change leaves the device in a non-functional state.

MitigationNetwork segmentation and access controls should be implemented to restrict unauthorized access to port 503. If available, apply vendor-supplied firmware updates. Consider implementing Modbus authentication or deploying a firewall/IDS to detect and block the anomalous register write sequence.

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
Diris M 70 FirmwareOperating system
Affected:= 1.6.9

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Query the Socomec DIRIS Digiware M-70 device for its firmware version through its web interface, SNMP, or Modbus registers to confirm it is version 1.6.9
    Affected if The device is a Socomec DIRIS Digiware M-70 running firmware version 1.6.9 exactly
  2. Verify Modbus TCP service is enabled
    Check if the Modbus TCP service is enabled on the device. This is typically configured in the device network settings or web interface under Modbus communication parameters
    Affected if Modbus TCP functionality is enabled on the device
  3. Confirm port 503 is accessible
    Scan the device network port 503 (TCP) to determine if the Modbus TCP service is exposed and reachable. Use a command like 'nmap -p 503 <device_ip>' or 'telnet <device_ip> 503'
    Affected if Port 503 is open and accessible from the network where an attacker could send the malicious packet sequence
  4. Check network exposure of Modbus service
    Evaluate whether the device with port 503 open is accessible from untrusted networks or if proper network segmentation is in place to restrict access to authorized systems only
    Affected if The Modbus TCP service on port 503 is accessible from untrusted or unauthenticated network segments

A user is affected if they have a Socomec DIRIS Digiware M-70 device running firmware version 1.6.9 with Modbus TCP enabled and port 503 accessible from a network where unauthenticated attackers can reach it.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Network segmentation and access controls should be implemented to restrict unauthorized access to port 503. If available, apply vendor-supplied firmware updates. Consider implementing Modbus authentication or deploying a firewall/IDS to detect and block the anomalous register write sequence.

Fix this in Diris M 70 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54850 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54850 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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