Summary
PPT30 OPC-UA Server has issues handling concurrent connections
Notes
Summary: B&R is aware of a vulnerability in the product versions listed as affected in the advisory.
An attacker who successfully exploits this vulnerability could make the OPC-UA server of the product inaccessible.
Support: For additional instructions and support please contact your local B&R service organization. For contact information, see https://www.br-automation.com/en/about-us/locations/.
Information about ABB’s cyber security program and capabilities can be found at www.abb.com/cybersecurity.
Notice: The information in this document is subject to change without notice, and should not be construed as a commitment by B&R.
B&R provides no warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, for the information contained in this document, and assumes no responsibility for any errors that may appear in this document. In no event shall B&R or any of its suppliers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, or from the use of any hardware or software described in this document, even if B&R or its suppliers have been advised of the possibility of such damages.
This document and parts hereof must not be reproduced or copied without written permission from B&R, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose.
All rights to registrations and trademarks reside with their respective owners.
General security recommendations: For any installation of software related ABB products we strongly recommend the following (non-exhaustive) list of cyber security practices:
- Isolate special purpose networks (e.g. for automation systems) and remote devices behind firewalls and separate them from any general purpose network (e.g. office or home networks).
- Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.
- Never connect programming software or computers containing programing software to any network other than the network for the devices that it is intended for.
- Scan all data imported into your environment before use to detect potential malware infections.
- Minimize network exposure for all applications and endpoints to ensure that they are not accessible from the Internet unless they are designed for such exposure and the intended use requires such.
- Ensure all nodes are always up to date in terms of installed software, operating system, and firmware patches as well as anti-virus and firewall.
- When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.
For more information on recommended practices, please refer to the following documents listed in the reference section:
- Defense in Depth for B&R products
Purpose: B&R has a rigorous internal cyber security continuous improvement process which involves regular testing with industry leading tools and periodic assessments to identify potential product issues. Occasionally an issue is determined to be a design or coding flaw with implications that may impact product cyber security.
When a potential product vulnerability is identified or reported, B&R immediately initiates our vulnerability handling process. This entails validating if the issue is in fact a product issue, identifying root causes, determining what related products may be impacted, developing a remediation, and notifying end users and governmental organizations.
The resulting Cyber Security Advisory intends to notify customers of the vulnerability and provide details on which products are impacted, how to mitigate the vulnerability or explain workarounds that minimize the potential risk as much as possible. The release of a Cyber Security Advisory should not be misconstrued as an affirmation or indication of an active threat or ongoing campaign targeting the products mentioned here. If B&R is aware of any specific threats, it will be clearly mentioned in the communication.
The publication of this Cyber Security Advisory is an example of B&R’s commitment to the user community in support of this critical topic. Responsible disclosure is an important element in the chain of trust we work to maintain with our many customers. The release of an Advisory provides timely information which is essential to help ensure our customers are fully informed.
Frequently asked questions: What causes the vulnerability?
- The vulnerability is caused by insufficient handling of resources by the OPC-UA Server used by the PPT30 Operating System.
What is PPT 30 Operating System
- The PPT30 Operating System is the firmware required to use the B&R PPT30 hardware products.
What might an attacker use the vulnerability to do?
- An attacker who successfully exploited this vulnerability could cause other users are no longer able to connect to the OPC-UA server on impacted devices.
How could an attacker exploit the vulnerability?
- An attacker could exploit the vulnerability by sending messages to an affected system node. This would require that the attacker has access to the system network, by connecting to the network either directly or through a wrongly configured or penetrated firewall, or that he installs malicious software on a system node or otherwise infects the network with malicious software. Recommended practices help mitigate such attacks, see section Mitigating Factors above.
Could the vulnerability be exploited remotely?
- Yes, an attacker who has network access to an affected system node could exploit this vulnerability. Recommended practices include that process control systems are physically protected, have no direct connections to the Internet, and are separated from other networks by means of a firewall system that has a minimal number of ports exposed.
When this security advisory was issued, had this vulnerability been publicly disclosed?
- No, B&R discovered the vulnerabilities through its own security analysis.
When this security advisory was issued, had B&R received any reports that this vulnerability was being exploited?
- No, B&R had not received any information indicating that this vulnerability had been exploited when this security advisory was originally issued
An Allocation of Resources Without Limits or Throttling vulnerability in the OPC-UA Server used in PPT30 Operating System versions before 1.8.0 may be used by an unauthenticated network-based at-tacker to permanently prevent legitimate users from interacting with the service.
CWE-770 - Allocation of Resources Without Limits or ThrottlingAffected products
Fixed
1 product
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
B&R Industrial Automation GmbH PPT30 Operating System 1.8.0
B&R Industrial Automation GmbH / PPT30 Operating System
|
1.8.0 |
Known affected
1 product
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
B&R Industrial Automation GmbH PPT30 Operating System <1.8.0
B&R Industrial Automation GmbH / PPT30 Operating System
|
<1.8.0 |
Vendor Fix
Mitigation
|
References
4 references
{
"document": {
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "en",
"notes": [
{
"category": "summary",
"text": "B\u0026R is aware of a vulnerability in the product versions listed as affected in the advisory.\n\nAn attacker who successfully exploits this vulnerability could make the OPC-UA server of the product inaccessible.\n\n",
"title": "Summary"
},
{
"category": "other",
"text": "For additional instructions and support please contact your local B\u0026R service organization. For contact information, see https://www.br-automation.com/en/about-us/locations/.\n\nInformation about ABB\u2019s cyber security program and capabilities can be found at www.abb.com/cybersecurity.\n\n\n",
"title": "Support"
},
{
"category": "legal_disclaimer",
"text": "The information in this document is subject to change without notice, and should not be construed as a commitment by B\u0026R.\n\nB\u0026R provides no warranty, express or implied, including warranties of merchantability and fitness for a particular purpose, for the information contained in this document, and assumes no responsibility for any errors that may appear in this document. In no event shall B\u0026R or any of its suppliers be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, or from the use of any hardware or software described in this document, even if B\u0026R or its suppliers have been advised of the possibility of such damages.\n\nThis document and parts hereof must not be reproduced or copied without written permission from B\u0026R, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose.\n\nAll rights to registrations and trademarks reside with their respective owners.",
"title": "Notice"
},
{
"category": "other",
"text": "For any installation of software related ABB products we strongly recommend the following (non-exhaustive) list of cyber security practices:\n\n- Isolate special purpose networks (e.g. for automation systems) and remote devices behind firewalls and separate them from any general purpose network (e.g. office or home networks).\n\n- Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.\n\n- Never connect programming software or computers containing programing software to any network other than the network for the devices that it is intended for.\n\n- Scan all data imported into your environment before use to detect potential malware infections.\n\n- Minimize network exposure for all applications and endpoints to ensure that they are not accessible from the Internet unless they are designed for such exposure and the intended use requires such.\n\n- Ensure all nodes are always up to date in terms of installed software, operating system, and firmware patches as well as anti-virus and firewall.\n\n- When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices.\n\nFor more information on recommended practices, please refer to the following documents listed in the reference section:\n\n- Defense in Depth for B\u0026R products\n \n",
"title": "General security recommendations"
},
{
"category": "other",
"text": "B\u0026R has a rigorous internal cyber security continuous improvement process which involves regular testing with industry leading tools and periodic assessments to identify potential product issues. Occasionally an issue is determined to be a design or coding flaw with implications that may impact product cyber security.\n\nWhen a potential product vulnerability is identified or reported, B\u0026R immediately initiates our vulnerability handling process. This entails validating if the issue is in fact a product issue, identifying root causes, determining what related products may be impacted, developing a remediation, and notifying end users and governmental organizations.\n\nThe resulting Cyber Security Advisory intends to notify customers of the vulnerability and provide details on which products are impacted, how to mitigate the vulnerability or explain workarounds that minimize the potential risk as much as possible. The release of a Cyber Security Advisory should not be misconstrued as an affirmation or indication of an active threat or ongoing campaign targeting the products mentioned here. If B\u0026R is aware of any specific threats, it will be clearly mentioned in the communication.\n\nThe publication of this Cyber Security Advisory is an example of B\u0026R\u2019s commitment to the user community in support of this critical topic. Responsible disclosure is an important element in the chain of trust we work to maintain with our many customers. The release of an Advisory provides timely information which is essential to help ensure our customers are fully informed.",
"title": "Purpose"
},
{
"category": "faq",
"text": "What causes the vulnerability?\n- The vulnerability is caused by insufficient handling of resources by the OPC-UA Server used by the PPT30 Operating System.\n\nWhat is PPT 30 Operating System\n- The PPT30 Operating System is the firmware required to use the B\u0026R PPT30 hardware products.\n\nWhat might an attacker use the vulnerability to do?\n- An attacker who successfully exploited this vulnerability could cause other users are no longer able to connect to the OPC-UA server on impacted devices.\n\nHow could an attacker exploit the vulnerability?\n- An attacker could exploit the vulnerability by sending messages to an affected system node. This would require that the attacker has access to the system network, by connecting to the network either directly or through a wrongly configured or penetrated firewall, or that he installs malicious software on a system node or otherwise infects the network with malicious software. Recommended practices help mitigate such attacks, see section Mitigating Factors above.\n\nCould the vulnerability be exploited remotely? \n- Yes, an attacker who has network access to an affected system node could exploit this vulnerability. Recommended practices include that process control systems are physically protected, have no direct connections to the Internet, and are separated from other networks by means of a firewall system that has a minimal number of ports exposed. \n\nWhen this security advisory was issued, had this vulnerability been publicly disclosed?\n- No, B\u0026R discovered the vulnerabilities through its own security analysis. \n\nWhen this security advisory was issued, had B\u0026R received any reports that this vulnerability was being exploited?\n- No, B\u0026R had not received any information indicating that this vulnerability had been exploited when this security advisory was originally issued \n",
"title": "Frequently asked questions"
}
],
"publisher": {
"category": "vendor",
"name": "ABB PSIRT",
"namespace": "https://www.abb.com/global/en/company/about/cybersecurity/alerts-and-notifications"
},
"references": [
{
"category": "self",
"summary": "B\u0026R CYBERSECURITY ADVISORY - PDF Version ",
"url": "https://br-cws-assets.de-fra-1.linodeobjects.com/SA25P006-0eec719c.pdf"
},
{
"category": "self",
"summary": "B\u0026R CYBERSECURITY ADVISORY - CSAF Version ",
"url": "https://psirt.abb.com/csaf/2026/sa25p006.json"
},
{
"summary": "Defense in Depth for B\u0026R products",
"url": "https://www.br-automation.com/fileadmin/Cyber_Security_-_Defense_in_Depth_for_BR_Products-bdd37e82.pdf"
}
],
"title": "PPT30 OPC-UA Server has issues handling concurrent connections",
"tracking": {
"current_release_date": "2026-05-26T00:30:00.000Z",
"generator": {
"date": "2026-05-26T10:44:46.225Z",
"engine": {
"name": "Secvisogram",
"version": "2.6.2"
}
},
"id": "SA25P006",
"initial_release_date": "2026-05-26T00:30:00.000Z",
"revision_history": [
{
"date": "2026-05-26T00:30:00.000Z",
"legacy_version": "A",
"number": "1",
"summary": "Initial version."
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c1.8.0",
"product": {
"name": "B\u0026R Industrial Automation GmbH PPT30 Operating System \u003c1.8.0",
"product_id": "AV1"
}
},
{
"category": "product_version",
"name": "1.8.0",
"product": {
"name": "B\u0026R Industrial Automation GmbH PPT30 Operating System 1.8.0",
"product_id": "FX1"
}
}
],
"category": "product_name",
"name": "PPT30 Operating System"
}
],
"category": "vendor",
"name": "B\u0026R Industrial Automation GmbH"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2025-11482",
"cwe": {
"id": "CWE-770",
"name": "Allocation of Resources Without Limits or Throttling"
},
"notes": [
{
"category": "description",
"text": "An Allocation of Resources Without Limits or Throttling vulnerability in the OPC-UA Server used in PPT30 Operating System versions before 1.8.0 may be used by an unauthenticated network-based at-tacker to permanently prevent legitimate users from interacting with the service.",
"title": "CVE description"
}
],
"product_status": {
"fixed": [
"FX1"
],
"known_affected": [
"AV1"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2025-11482",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-11482"
}
],
"remediations": [
{
"category": "vendor_fix",
"details": "The problem is corrected in the following product versions:\n\nPPT30 Operating System 1.8.0\n\nThe OPC-UA server is not activated by default. B\u0026R recommends that customers with the OPC-UA Server enabled to install the update at their earliest opportunity. \n\nThe process to install updates is described in the user manual. The step to identify the installed product version is described in the user manual.\n",
"product_ids": [
"AV1"
]
},
{
"category": "mitigation",
"details": "The optional OPC-UA server is not activated by default. The OPC-UA server shall only be activated, if required.\n\nPPT30 products are intended to operate at Levels 1 and 2 of the ABB ICS Cyber Security Reference Architecture. To restrict access to the OPC-UA server exclusively to trusted IP addresses, configure the South Firewall and/or the Control Network Firewall accordingly, and properly segment the network where the PPT30 operates. Additionally, ensure that the physical network interfaces assigned to the same logical network as the PPT30 are accessible only to authorized personnel.\n\nRefer to section \u201cGeneral security recommendations\u201d for further advise on how to keep your system secure.\n",
"product_ids": [
"AV1"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"environmentalScore": 6.5,
"environmentalSeverity": "MEDIUM",
"exploitCodeMaturity": "UNPROVEN",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"remediationLevel": "OFFICIAL_FIX",
"reportConfidence": "CONFIRMED",
"scope": "UNCHANGED",
"temporalScore": 6.5,
"temporalSeverity": "MEDIUM",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C",
"version": "3.1"
},
"products": [
"AV1"
]
}
],
"title": "CVE-2025-11482"
}
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…