VulnerabilityPublished 12 Aug 2025

CVE-2025-30034: Siemens SIMATIC RTLS Locating Manager · Reachable Assertion

Affects Siemens SIMATIC RTLS Locating ManagerSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

6.2Medium

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Aug 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 26 Oct 2026.

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 or the CVSS exploit maturity 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 SIMATIC RTLS Locating Manager	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Restrict local access to systems running SIMATIC RTLS Locating Manager by enforcing strict access controls and network segmentation to limit who can connect to the loopback interface. 2) Monitor and audit local user activities to detect any unauthorized attempts to interact with the vulnerable service. 4) Implement host-based intrusion detection systems (HIDS) to detect anomalous local traffic or assertion failures related to the RTLS service. 5) Employ application whitelisting and endpoint protection to prevent unauthorized code execution or exploitation attempts. 6) Consider temporary compensating controls such as disabling or isolating the RTLS Locating Manager service if feasible, until a patch is applied. 7) Conduct internal security awareness training focusing on the risks of local privilege escalation and insider threats to reduce the likelihood of exploitation.

Description

A vulnerability has been identified in SIMATIC RTLS Locating Manager (All versions < V3.3). Affected devices do not properly validate input sent to its listening port on the local loopback interface. This could allow an unauthenticated local attacker to cause a denial of service condition.

Impact

For European organizations, especially those in industrial automation, manufacturing, logistics, and critical infrastructure sectors using Siemens SIMATIC RTLS Locating Manager, this vulnerability poses a risk of service disruption. The denial of service could interrupt real-time location tracking of assets, personnel, or equipment, leading to operational inefficiencies, safety risks, and potential financial losses. Since the vulnerability requires local access, the threat is primarily from insider threats or attackers who have already gained initial foothold within the network. However, the disruption of availability in industrial environments can have cascading effects, including delayed production, impaired safety monitoring, and reduced situational awareness. Organizations relying on RTLS for compliance or safety-critical functions may face regulatory and operational challenges if the system becomes unavailable. Although there is no direct confidentiality or integrity impact, the availability impact alone can be significant in time-sensitive industrial contexts.

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Aug 2025, 11:52 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats