CVE-2025-54848: CWE-306: Missing Authentication for Critical Function in Socomec DIRIS Digiware M-70
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 TCP messages to port 502 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.
AI Analysis
Technical Summary
CVE-2025-54848 identifies a critical vulnerability in the Socomec DIRIS Digiware M-70 power monitoring device, specifically version 1.6.9. The vulnerability arises from the lack of authentication on critical Modbus TCP and Modbus RTU over TCP functions, allowing an attacker to remotely induce a denial-of-service (DoS) condition. The attack exploits the Write Single Register function (function code 6) on Modbus TCP port 502 by sending a carefully crafted sequence of messages targeting specific registers. Initially, a message writes the value 1000 to register 58112, signaling an impending configuration change. Subsequently, a message sets a new Modbus address by writing to register 29440. Finally, a message writing the value 161 to register 57856 commits the configuration change. This sequence causes the device to enter a denial-of-service state, rendering it non-functional. The vulnerability is classified under CWE-306, indicating missing authentication for critical functions. The CVSS v3.1 base score is 7.5 (high), reflecting network attack vector, no privileges or user interaction required, and a significant impact on availability. No patches or mitigations are currently linked, and no exploits have been observed in the wild, but the vulnerability poses a substantial risk to operational continuity in environments using this device.
Potential Impact
The primary impact of CVE-2025-54848 is a denial-of-service condition that disrupts the availability of the Socomec DIRIS Digiware M-70 device. For European organizations, especially those in critical infrastructure sectors such as energy, manufacturing, and utilities, this can lead to loss of real-time power monitoring and management capabilities. Such disruption can cause operational inefficiencies, delayed fault detection, and potential cascading failures in power distribution systems. Given the device’s role in monitoring electrical parameters, prolonged unavailability could affect compliance with regulatory requirements for power quality and safety. Additionally, the lack of authentication means that any attacker with network access can exploit this vulnerability, increasing the risk of targeted attacks or accidental disruptions. The impact is heightened in environments where these devices are exposed to less controlled networks or where network segmentation is insufficient. The operational downtime and potential need for manual intervention to restore device functionality could incur significant costs and safety risks.
Mitigation Recommendations
To mitigate CVE-2025-54848, organizations should implement the following specific measures: 1) Immediately restrict network access to the Modbus TCP port 502 on DIRIS Digiware M-70 devices by applying firewall rules or network segmentation to limit exposure to trusted management networks only. 2) Deploy intrusion detection or prevention systems (IDS/IPS) capable of monitoring Modbus traffic for anomalous sequences indicative of this attack pattern. 3) If possible, disable Modbus TCP or RTU over TCP interfaces when not required or replace them with more secure communication protocols that support authentication and encryption. 4) Work with Socomec support channels to obtain firmware updates or patches addressing this vulnerability as they become available. 5) Implement network-level authentication mechanisms such as VPNs or TLS tunnels to protect Modbus communications. 6) Conduct regular audits of device configurations and network access controls to ensure no unauthorized changes or exposures exist. 7) Prepare incident response plans that include steps to recover from device DoS conditions, including manual reset procedures and fallback monitoring solutions. These targeted actions go beyond generic advice by focusing on controlling network exposure and monitoring Modbus protocol behavior specific to this vulnerability.
Affected Countries
Germany, France, Italy, United Kingdom, Spain, Netherlands, Belgium, Poland, Sweden, Switzerland
CVE-2025-54848: CWE-306: Missing Authentication for Critical Function in Socomec DIRIS Digiware M-70
Description
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 TCP messages to port 502 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.
AI-Powered Analysis
Technical Analysis
CVE-2025-54848 identifies a critical vulnerability in the Socomec DIRIS Digiware M-70 power monitoring device, specifically version 1.6.9. The vulnerability arises from the lack of authentication on critical Modbus TCP and Modbus RTU over TCP functions, allowing an attacker to remotely induce a denial-of-service (DoS) condition. The attack exploits the Write Single Register function (function code 6) on Modbus TCP port 502 by sending a carefully crafted sequence of messages targeting specific registers. Initially, a message writes the value 1000 to register 58112, signaling an impending configuration change. Subsequently, a message sets a new Modbus address by writing to register 29440. Finally, a message writing the value 161 to register 57856 commits the configuration change. This sequence causes the device to enter a denial-of-service state, rendering it non-functional. The vulnerability is classified under CWE-306, indicating missing authentication for critical functions. The CVSS v3.1 base score is 7.5 (high), reflecting network attack vector, no privileges or user interaction required, and a significant impact on availability. No patches or mitigations are currently linked, and no exploits have been observed in the wild, but the vulnerability poses a substantial risk to operational continuity in environments using this device.
Potential Impact
The primary impact of CVE-2025-54848 is a denial-of-service condition that disrupts the availability of the Socomec DIRIS Digiware M-70 device. For European organizations, especially those in critical infrastructure sectors such as energy, manufacturing, and utilities, this can lead to loss of real-time power monitoring and management capabilities. Such disruption can cause operational inefficiencies, delayed fault detection, and potential cascading failures in power distribution systems. Given the device’s role in monitoring electrical parameters, prolonged unavailability could affect compliance with regulatory requirements for power quality and safety. Additionally, the lack of authentication means that any attacker with network access can exploit this vulnerability, increasing the risk of targeted attacks or accidental disruptions. The impact is heightened in environments where these devices are exposed to less controlled networks or where network segmentation is insufficient. The operational downtime and potential need for manual intervention to restore device functionality could incur significant costs and safety risks.
Mitigation Recommendations
To mitigate CVE-2025-54848, organizations should implement the following specific measures: 1) Immediately restrict network access to the Modbus TCP port 502 on DIRIS Digiware M-70 devices by applying firewall rules or network segmentation to limit exposure to trusted management networks only. 2) Deploy intrusion detection or prevention systems (IDS/IPS) capable of monitoring Modbus traffic for anomalous sequences indicative of this attack pattern. 3) If possible, disable Modbus TCP or RTU over TCP interfaces when not required or replace them with more secure communication protocols that support authentication and encryption. 4) Work with Socomec support channels to obtain firmware updates or patches addressing this vulnerability as they become available. 5) Implement network-level authentication mechanisms such as VPNs or TLS tunnels to protect Modbus communications. 6) Conduct regular audits of device configurations and network access controls to ensure no unauthorized changes or exposures exist. 7) Prepare incident response plans that include steps to recover from device DoS conditions, including manual reset procedures and fallback monitoring solutions. These targeted actions go beyond generic advice by focusing on controlling network exposure and monitoring Modbus protocol behavior specific to this vulnerability.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- talos
- Date Reserved
- 2025-07-31T15:17:58.545Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 692db927f910530b0eb0723a
Added to database: 12/1/2025, 3:49:59 PM
Last enriched: 12/1/2025, 4:06:04 PM
Last updated: 12/5/2025, 12:11:03 AM
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-13373: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in Advantech iView
HighCVE-2025-66564: CWE-405: Asymmetric Resource Consumption (Amplification) in sigstore timestamp-authority
HighCVE-2025-66559: CWE-129: Improper Validation of Array Index in taikoxyz taiko-mono
HighCVE-2025-66563: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in monkeytypegame monkeytype
HighCVE-2025-66561: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Syslifters sysreptor
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.