CVE-2025-54849: 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 single Modbus TCP message to port 502 using the Write Single Register function code (6) to write the value 1 to register 4352. This action changes the Modbus address to 15. After this message is sent, the device will be in a denial-of-service state.
AI Analysis
Technical Summary
CVE-2025-54849 is a vulnerability classified under CWE-306 (Missing Authentication for Critical Function) affecting Socomec DIRIS Digiware M-70 devices running firmware version 1.6.9. The vulnerability resides in the Modbus TCP and Modbus RTU over TCP communication protocols implemented by the device. Specifically, the device listens on the standard Modbus TCP port 502 and accepts commands without authentication. An attacker can exploit this by sending a single Modbus TCP Write Single Register (function code 6) message targeting register 4352 with the value 1. This action changes the device's Modbus address to 15, which leads the device into a denial-of-service (DoS) state, rendering it unresponsive or non-functional. The attack requires no privileges, no user interaction, and can be performed remotely over the network, making it easy to exploit. The vulnerability impacts availability only, with no direct impact on confidentiality or integrity. The CVSS v3.1 base score is 7.5, reflecting high severity due to ease of exploitation and significant operational impact. No patches or firmware updates have been published at the time of disclosure, and no known exploits have been observed in the wild. The vulnerability highlights the risk of unauthenticated critical functions in industrial control devices, especially those using legacy protocols like Modbus without security enhancements.
Potential Impact
For European organizations, especially those operating in industrial automation, energy management, and critical infrastructure sectors, this vulnerability poses a significant risk of operational disruption. The Socomec DIRIS Digiware M-70 is used for power monitoring and energy management, often integrated into industrial control systems (ICS) and building management systems (BMS). A successful exploitation could cause device downtime, loss of monitoring capabilities, and potential cascading effects on dependent systems. This could lead to reduced situational awareness, delayed incident response, and in worst cases, physical damage or safety hazards if power systems are improperly managed. The lack of authentication means that any attacker with network access can trigger the DoS, increasing the attack surface. Given the increasing reliance on smart energy management in Europe’s push for energy efficiency and grid modernization, the impact could be widespread. Additionally, disruption in critical infrastructure could have regulatory and reputational consequences for affected organizations.
Mitigation Recommendations
1. Network Segmentation: Isolate Socomec DIRIS Digiware M-70 devices on dedicated network segments with strict firewall rules to restrict access to port 502 only to trusted management systems. 2. Access Controls: Implement strong network access controls and limit Modbus TCP traffic to authorized personnel and systems. 3. Monitoring and Detection: Deploy intrusion detection systems (IDS) or network monitoring tools capable of inspecting Modbus traffic to detect anomalous Write Single Register commands targeting register 4352 or unusual Modbus address changes. 4. Vendor Coordination: Engage with Socomec for firmware updates or patches addressing this vulnerability and apply them promptly once available. 5. Incident Response Planning: Prepare response procedures for potential DoS events affecting these devices to minimize downtime. 6. Disable Unused Protocols: If Modbus TCP or RTU over TCP is not required, disable these services on the device to reduce attack surface. 7. Network Encryption and Authentication: Where possible, implement secure tunneling or VPNs for Modbus traffic to add authentication and confidentiality layers, compensating for protocol weaknesses. 8. Physical Security: Ensure physical security of devices to prevent local tampering that could facilitate exploitation.
Affected Countries
Germany, France, Italy, United Kingdom, Netherlands, Belgium, Spain, Poland, Sweden, Czech Republic
CVE-2025-54849: 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 single Modbus TCP message to port 502 using the Write Single Register function code (6) to write the value 1 to register 4352. This action changes the Modbus address to 15. After this message is sent, the device will be in a denial-of-service state.
AI-Powered Analysis
Technical Analysis
CVE-2025-54849 is a vulnerability classified under CWE-306 (Missing Authentication for Critical Function) affecting Socomec DIRIS Digiware M-70 devices running firmware version 1.6.9. The vulnerability resides in the Modbus TCP and Modbus RTU over TCP communication protocols implemented by the device. Specifically, the device listens on the standard Modbus TCP port 502 and accepts commands without authentication. An attacker can exploit this by sending a single Modbus TCP Write Single Register (function code 6) message targeting register 4352 with the value 1. This action changes the device's Modbus address to 15, which leads the device into a denial-of-service (DoS) state, rendering it unresponsive or non-functional. The attack requires no privileges, no user interaction, and can be performed remotely over the network, making it easy to exploit. The vulnerability impacts availability only, with no direct impact on confidentiality or integrity. The CVSS v3.1 base score is 7.5, reflecting high severity due to ease of exploitation and significant operational impact. No patches or firmware updates have been published at the time of disclosure, and no known exploits have been observed in the wild. The vulnerability highlights the risk of unauthenticated critical functions in industrial control devices, especially those using legacy protocols like Modbus without security enhancements.
Potential Impact
For European organizations, especially those operating in industrial automation, energy management, and critical infrastructure sectors, this vulnerability poses a significant risk of operational disruption. The Socomec DIRIS Digiware M-70 is used for power monitoring and energy management, often integrated into industrial control systems (ICS) and building management systems (BMS). A successful exploitation could cause device downtime, loss of monitoring capabilities, and potential cascading effects on dependent systems. This could lead to reduced situational awareness, delayed incident response, and in worst cases, physical damage or safety hazards if power systems are improperly managed. The lack of authentication means that any attacker with network access can trigger the DoS, increasing the attack surface. Given the increasing reliance on smart energy management in Europe’s push for energy efficiency and grid modernization, the impact could be widespread. Additionally, disruption in critical infrastructure could have regulatory and reputational consequences for affected organizations.
Mitigation Recommendations
1. Network Segmentation: Isolate Socomec DIRIS Digiware M-70 devices on dedicated network segments with strict firewall rules to restrict access to port 502 only to trusted management systems. 2. Access Controls: Implement strong network access controls and limit Modbus TCP traffic to authorized personnel and systems. 3. Monitoring and Detection: Deploy intrusion detection systems (IDS) or network monitoring tools capable of inspecting Modbus traffic to detect anomalous Write Single Register commands targeting register 4352 or unusual Modbus address changes. 4. Vendor Coordination: Engage with Socomec for firmware updates or patches addressing this vulnerability and apply them promptly once available. 5. Incident Response Planning: Prepare response procedures for potential DoS events affecting these devices to minimize downtime. 6. Disable Unused Protocols: If Modbus TCP or RTU over TCP is not required, disable these services on the device to reduce attack surface. 7. Network Encryption and Authentication: Where possible, implement secure tunneling or VPNs for Modbus traffic to add authentication and confidentiality layers, compensating for protocol weaknesses. 8. Physical Security: Ensure physical security of devices to prevent local tampering that could facilitate exploitation.
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: 692db927f910530b0eb0723d
Added to database: 12/1/2025, 3:49:59 PM
Last enriched: 12/8/2025, 5:06:50 PM
Last updated: 1/18/2026, 2:33:30 PM
Views: 31
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-2026-1122: SQL Injection in Yonyou KSOA
MediumCVE-2026-1121: SQL Injection in Yonyou KSOA
MediumCVE-2026-1120: SQL Injection in Yonyou KSOA
MediumCVE-2026-1119: SQL Injection in itsourcecode Society Management System
MediumCVE-2026-1118: SQL Injection in itsourcecode Society Management System
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.