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-55222: CWE-306: Missing Authentication for Critical Function in Socomec DIRIS Digiware M-70

0
High
VulnerabilityCVE-2025-55222cvecve-2025-55222cwe-306
Published: Mon Dec 01 2025 (12/01/2025, 15:25:07 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 USB Function functionality of Socomec DIRIS Digiware M-70 1.6.9. A specially crafted network packet can lead to a denial of service. An attacker can send an unauthenticated packet to trigger this vulnerability.This vulnerability is specific to the malicious message sent via Modbus RTU over TCP on port 503.

AI-Powered Analysis

AILast updated: 12/01/2025, 16:04:38 UTC

Technical Analysis

CVE-2025-55222 identifies a denial of service (DoS) vulnerability in the Socomec DIRIS Digiware M-70, specifically version 1.6.9. The vulnerability arises from missing authentication controls (CWE-306) in the Modbus TCP and Modbus RTU over TCP USB Function implementation, which listens on port 503. An attacker can send a specially crafted Modbus RTU over TCP packet without any authentication or user interaction to trigger a crash or service disruption, leading to denial of service. The Modbus protocol is widely used in industrial control systems (ICS) and energy management devices for communication between controllers and field devices. Because the device does not verify the authenticity of incoming Modbus packets, it is susceptible to unauthenticated remote attacks. The CVSS v3.1 score of 8.6 reflects the high impact on availability (A:H), with no impact on confidentiality or integrity, and the ease of exploitation (network vector, no privileges or user interaction required). The scope is considered changed (S:C) because the vulnerability affects components beyond the vulnerable device itself, potentially impacting connected systems. No patches or mitigations have been officially released at the time of publication, and no exploits are known in the wild. This vulnerability could be exploited by attackers to disrupt monitoring and control functions in critical infrastructure environments where the DIRIS Digiware M-70 is deployed.

Potential Impact

For European organizations, especially those in industrial, energy, and critical infrastructure sectors, this vulnerability poses a significant risk to operational continuity. The Socomec DIRIS Digiware M-70 is used for energy monitoring and management, and a denial of service could interrupt data collection, alarm generation, and control processes. This disruption could lead to delayed incident response, inaccurate energy usage data, and potential cascading failures in automated control systems. Given the lack of authentication, attackers can remotely exploit this vulnerability without prior access, increasing the attack surface. The impact is primarily on availability, which is critical in industrial environments where uptime and real-time monitoring are essential. Organizations relying on these devices for compliance with EU energy efficiency directives or operational safety may face regulatory and financial consequences if disruptions occur. Additionally, the vulnerability could be leveraged as part of a broader attack campaign targeting European energy grids or manufacturing facilities, amplifying its impact.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Immediately restrict network access to port 503 (Modbus RTU over TCP) on DIRIS Digiware M-70 devices by applying firewall rules and network segmentation to isolate these devices from untrusted networks. 2) Deploy intrusion detection/prevention systems (IDS/IPS) with Modbus protocol anomaly detection capabilities to identify and block malformed or unauthorized Modbus packets. 3) Enforce strict access control policies limiting Modbus communication to authorized management stations only. 4) Monitor network traffic for unusual Modbus activity patterns indicative of scanning or exploitation attempts. 5) Engage with Socomec support channels to obtain firmware updates or patches as they become available, and plan for timely deployment. 6) Consider implementing additional authentication or encryption layers at the network level (e.g., VPN tunnels) to protect Modbus communications where possible. 7) Conduct regular security audits and penetration tests focused on industrial control system components to identify and remediate similar vulnerabilities proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
talos
Date Reserved
2025-08-11T15:04:59.033Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692db927f910530b0eb07249

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

Last enriched: 12/1/2025, 4:04:38 PM

Last updated: 12/5/2025, 12:11:03 AM

Views: 39

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats