CVE-2025-40802VulnerabilityPublished 9 Sep 2025

CVE-2025-40802: Siemens RUGGEDCOM RST2428P · Uncontrolled Resource Consumption

Affects Siemens RUGGEDCOM RST2428PSource CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.1Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Siemens RUGGEDCOM RST2428P	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should implement the following specific measures: 1) Network Segmentation: Ensure strict segmentation of OT and ICS networks from corporate and external networks to limit attacker access to the device's local network. 2) Rate Limiting and Traffic Filtering: Deploy network devices capable of detecting and limiting excessive query requests to the RUGGEDCOM device, preventing resource exhaustion. 3) Monitoring and Anomaly Detection: Implement continuous monitoring of network traffic to identify unusual spikes in query requests targeting the RUGGEDCOM RST2428P. 4) Access Control: Restrict management and query access to the device to authorized personnel and systems only, using strong authentication and access control lists. 5) Vendor Coordination: Engage with Siemens for updates on patches or firmware upgrades addressing this vulnerability and plan timely deployment once available. 6) Incident Response Planning: Prepare response procedures for temporary DoS events affecting industrial switches to minimize operational impact. 7) Physical Security: Ensure physical security controls to prevent unauthorized local network access to the device. These measures go beyond generic advice by focusing on the specific attack vector (high volume query requests) and the operational context of industrial network devices.

Description

A vulnerability has been identified in RUGGEDCOM RST2428P (6GK6242-6PA00) (All versions). The affected device may be susceptible to resource exhaustion when subjected to high volumes of query requests. This could allow an attacker to cause a temporary denial of service, with the system recovering once the activity stops.

Impact

For European organizations, particularly those operating in critical infrastructure sectors such as energy, transportation, and manufacturing, this vulnerability poses a risk of temporary service disruption. The RUGGEDCOM RST2428P is widely deployed in industrial control systems (ICS) and operational technology (OT) networks, which are essential for maintaining continuous operations. A successful exploitation could lead to temporary denial of service conditions, causing delays or interruptions in data transmission and network management functions. While the impact is limited to availability and is temporary, even short outages in critical infrastructure can have cascading effects, including safety risks, financial losses, and regulatory non-compliance. The requirement for adjacent network access and high attack complexity reduces the likelihood of widespread exploitation but does not eliminate the risk, especially in environments where network segmentation is weak or where attackers have gained a foothold in the local network. European organizations must consider the potential operational disruptions and the importance of maintaining resilient industrial networks.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cert-portal.siemens.com/productcert/html/ssa-494539.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Sep 2025, 08:59 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats