Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-54851: CWE-306: Missing Authentication for Critical Function in Socomec DIRIS Digiware M-70

0
High
VulnerabilityCVE-2025-54851cvecve-2025-54851cwe-306
Published: Mon Dec 01 2025 (12/01/2025, 15:25:13 UTC)
Source: CVE Database V5
Vendor/Project: Socomec
Product: 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 503 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

AILast updated: 12/08/2025, 17:07:23 UTC

Technical Analysis

CVE-2025-54851 identifies a denial of service vulnerability in the Socomec DIRIS Digiware M-70 energy monitoring device, specifically version 1.6.9. The vulnerability resides in the Modbus TCP and Modbus RTU over TCP protocols implemented by the device. An attacker can exploit this by sending a specially crafted Modbus TCP message to port 503 without any authentication. The attack uses the Write Single Register function code (6) to write the value 1 to register 4352, which changes the device's Modbus address to 15. This change causes the device to enter a denial-of-service state, rendering it unresponsive or non-functional. The root cause is a missing authentication mechanism for this critical function, classified under CWE-306. The vulnerability has a CVSS 3.1 base score of 7.5, indicating high severity due to its network attack vector, low attack complexity, no privileges or user interaction required, and a high impact on availability. No patches or fixes have been released at the time of publication, and no active exploitation has been reported. The device is commonly used in industrial and energy monitoring environments, where Modbus protocols are standard for communication. The lack of authentication on critical Modbus commands exposes the device to remote attacks that can disrupt monitoring and control functions.

Potential Impact

For European organizations, particularly those in energy management, industrial automation, and critical infrastructure sectors, this vulnerability poses a significant risk of operational disruption. The denial of service can lead to loss of monitoring capabilities, inaccurate energy data collection, and potential cascading effects on automated control systems relying on the DIRIS Digiware M-70. This can affect energy efficiency, fault detection, and safety monitoring. In critical infrastructure environments such as power grids, manufacturing plants, and large commercial facilities, such disruptions can cause financial losses, regulatory non-compliance, and safety hazards. The ease of exploitation without authentication means that attackers with network access—potentially including insider threats or attackers who gain initial footholds in corporate networks—can cause outages remotely. Given the widespread use of Modbus protocols in European industrial environments, the impact could be broad, especially if network segmentation and access controls are insufficient.

Mitigation Recommendations

1. Implement strict network segmentation to isolate DIRIS Digiware M-70 devices from untrusted networks, especially the internet and general corporate LANs. 2. Restrict access to port 503 (Modbus TCP) using firewalls and access control lists to only trusted management systems. 3. Monitor Modbus traffic for anomalous or unauthorized Write Single Register commands, particularly to register 4352. 4. Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics for Modbus protocol abuse. 5. Where possible, disable unused Modbus functions or restrict write capabilities to authorized devices only. 6. Engage with Socomec for firmware updates or patches addressing this vulnerability and apply them promptly once available. 7. Conduct regular security audits and penetration testing focused on industrial control systems and Modbus communications. 8. Train operational technology (OT) staff on recognizing and responding to Modbus-related attacks. 9. Maintain an incident response plan tailored to industrial control system disruptions. 10. Consider deploying network-level authentication or encryption solutions (e.g., VPNs, TLS proxies) for Modbus communications if supported by the environment.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
talos
Date Reserved
2025-07-31T15:17:58.546Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692db927f910530b0eb07243

Added to database: 12/1/2025, 3:49:59 PM

Last enriched: 12/8/2025, 5:07:23 PM

Last updated: 1/19/2026, 4:41:13 AM

Views: 122

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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.

Latest Threats