External risk intelligence

B&R Automation Runtime SDM Improper Resource Locking Denial of Service

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2025-3450

The vulnerability affects B&R Automation Runtime, which is an industrial automation and control system component. While network-reachable, these systems are typically deployed within isolated industrial or operational technology networks and are rarely exposed directly to the public internet in common, secure deployment patterns.

Denial of Service

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

An Improper Resource Locking vulnerability exists in the SDM component of B&R Automation Runtime, potentially allowing an unauthenticated attacker to delete data and cause denial of service. This type of issue can disrupt critical operations by rendering systems unavailable.

  • Attackers can delete data causing service denial.
  • It impacts industrial automation systems.
  • Confirm relevance and exposure to operational technology.

Attack Path

How an attacker could exploit the issue

An attacker could reach the vulnerable component over the network without needing any prior access or authentication. By interacting with the SDM component, they could trigger a vulnerability that allows them to delete data, potentially leading to a denial of service.

  • Unauthenticated network access required.
  • Triggered by interacting with the SDM component.
  • Risk of data deletion and denial of service.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to delete data within the SDM component, leading to denial of service.

  • Data deletion in SDM.
  • Unauthenticated network access.
  • Service disruption.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects the SDM component of B&R Automation Runtime, impacting data integrity and availability. Given its critical nature and potential for unauthenticated network exploitation, immediate identification of affected systems is paramount. Infrastructure and operational technology teams are likely responsible for managing this component. The first practical step is to locate all instances of the affected technology, confirm their reachability and business criticality, and then engage the accountable owner to prioritize and plan remediation.

  • Infrastructure and OT teams should own remediation.
  • Verify system reachability and business criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is B&R Automation Runtime and its SDM component?

B&R Automation Runtime is a core software platform used in industrial settings to control machinery and automated processes. Within this, the System Diagnostics Manager (SDM) component provides web-based diagnostic and maintenance tools that allow engineers to monitor system health and configuration status.

What does Improper Resource Locking mean for CVE-2025-3450?

This vulnerability, classified as CWE-413, occurs when software fails to correctly manage access to shared data. In the context of CVE-2025-3450, it means the SDM component does not properly protect data resources, allowing an unauthorized party to manipulate or delete critical files that the system needs to function.

How can an attacker trigger this vulnerability?

An attacker triggers this by interacting with the SDM component over a network without needing a password or user account. Simply sending specific, unauthorized requests to the interface can cause the deletion of data. Legitimate, non-malicious interactions with SDM, such as standard diagnostic checks, do not trigger this error.

Is my system at risk if it is not on the public internet?

Halo Surface Signal indicates that while this flaw is reachable via network, these systems are usually in isolated industrial networks. If your device is on an internal OT network and not directly connected to the public internet, it is less likely to be reachable by external threats, though internal access still poses a risk.

What are the first steps to address this CVE?

Begin by creating an inventory of all B&R Automation Runtime instances in your environment. Determine which systems are running versions earlier than 6.3 or Q4.93. Assess the business criticality of those assets and coordinate with your OT or infrastructure teams to plan and apply the necessary vendor-provided updates.

References