3ADR011407
Vulnerability from csaf_abb - Published: 2025-04-30 00:00 - Updated: 2025-07-25 00:00Summary
ABB Automation Builder Vulnerabilities in user management and access control
Notes
Summary
ABB is aware of vulnerabilities in the product versions listed as affected in the following section.
An attacker who successfully exploited this vulnerability could overrule the Automation Builder’s user management. Workarounds to close the vulnerabilities are available.
Workarounds
Workarounds are specific measures that a user can take to help block an attack, for example, temporarily disabling the vulnerable feature may remove the exposure with well-known impact on functionality.
ABB has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they can help block known attack vectors. When a workaround reduces functionality, this is
identified below as “Impact of workaround”.
To exploit the vulnerabilities, access the project on file level is required. This can be prevented by the security settings of the Automation Builder projects, accessible via the menu “Project” → “Project
Settings…” → “Security”.
• CVE-2025-3394: In the project settings, set “Security” to “Integrity check”. This prevents anyone
to access or modify the content of the Automation Builder project file. Projects can be opened
and used without any limitations.
• CVE-2025-3395: In the project settings, set “Security” to “Encryption”. This prevents unauthorized users to open the project. Authorized users can open the project and with that exploit the
vulnerability
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.
Notice
The information in this document is subject to change without notice, and should not be construed as a
commitment by ABB.
ABB 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 ABB 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 ABB 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
ABB, 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
Support
For additional instructions and support please contact your local ABB service organization. For contact
information, see www.abb.com/contactcenters.
Information about ABB’s cyber security program and capabilities can be found at www.abb.com/cybersecurity.
Mitigating factors
Immediate workarounds to close the vulnerabilities are:
• CVE-2025-3394: In the project settings, set “Security” to “Integrity check”
• CVE-2025-3395: In the project settings, set “Security” to “Encryption”
ABB recommends that customers apply the workarounds at earliest convenience.
With the latest Automation Builder version (starting with version 2.8.1), the default for “Security” is set
to “Integrity check”. By keeping this default unchanged, CVE-2025-3394 cannot be exploited.
{
"document": {
"acknowledgments": [
{
"names": [
"Jiho Shin"
],
"organization": "Sungkyunkwan University"
}
],
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "En",
"notes": [
{
"category": "summary",
"text": "ABB is aware of vulnerabilities in the product versions listed as affected in the following section.\n\nAn attacker who successfully exploited this vulnerability could overrule the Automation Builder\u2019s user management. Workarounds to close the vulnerabilities are available.\n",
"title": "Summary"
},
{
"category": "general",
"text": "Workarounds are specific measures that a user can take to help block an attack, for example, temporarily disabling the vulnerable feature may remove the exposure with well-known impact on functionality.\nABB has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they can help block known attack vectors. When a workaround reduces functionality, this is\nidentified below as \u201cImpact of workaround\u201d.\n\nTo exploit the vulnerabilities, access the project on file level is required. This can be prevented by the security settings of the Automation Builder projects, accessible via the menu \u201cProject\u201d \u2192 \u201cProject\nSettings\u2026\u201d \u2192 \u201cSecurity\u201d.\n\n\u2022 CVE-2025-3394: In the project settings, set \u201cSecurity\u201d to \u201cIntegrity check\u201d. This prevents anyone\nto access or modify the content of the Automation Builder project file. Projects can be opened\nand used without any limitations.\n\n\u2022 CVE-2025-3395: In the project settings, set \u201cSecurity\u201d to \u201cEncryption\u201d. This prevents unauthorized users to open the project. Authorized users can open the project and with that exploit the\nvulnerability",
"title": "Workarounds"
},
{
"category": "other",
"text": "For any installation of software related ABB products we strongly recommend the following (non-exhaustive) list of cyber security practices:\n\u2013 Isolate special purpose networks (e.g. for automation systems) and remote devices behind firewalls\nand separate them from any general-purpose network (e.g. office or home networks).\n\u2013 Install physical controls so no unauthorized personnel can access your devices, components, peripheral equipment, and networks.\n\u2013 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\u2013 Scan all data imported into your environment before use to detect potential malware infections.\n\u2013 Minimize network exposure for all applications and endpoints to ensure that they are not accessible\nfrom the Internet unless they are designed for such exposure and the intended use requires such.\n\u2013 Ensure all nodes are always up to date in terms of installed software, operating system, and firmware\npatches as well as anti-virus and firewall.\n\u2013 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.",
"title": "General security recommendations"
},
{
"category": "legal_disclaimer",
"text": "The information in this document is subject to change without notice, and should not be construed as a\ncommitment by ABB.\nABB provides no warranty, express or implied, including warranties of merchantability and fitness for a\nparticular purpose, for the information contained in this document, and assumes no responsibility for\nany errors that may appear in this document. In no event shall ABB 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\nthis document, or from the use of any hardware or software described in this document, even if ABB or\nits suppliers have been advised of the possibility of such damages.\nThis document and parts hereof must not be reproduced or copied without written permission from\nABB, and the contents hereof must not be imparted to a third party nor used for any unauthorized purpose.\nAll rights to registrations and trademarks reside with their respective owners",
"title": "Notice"
},
{
"category": "other",
"text": "For additional instructions and support please contact your local ABB service organization. For contact\ninformation, see www.abb.com/contactcenters.\nInformation about ABB\u2019s cyber security program and capabilities can be found at www.abb.com/cybersecurity.",
"title": "Support"
},
{
"category": "general",
"text": "Immediate workarounds to close the vulnerabilities are:\n\n\u2022 CVE-2025-3394: In the project settings, set \u201cSecurity\u201d to \u201cIntegrity check\u201d\n\n\u2022 CVE-2025-3395: In the project settings, set \u201cSecurity\u201d to \u201cEncryption\u201d\nABB recommends that customers apply the workarounds at earliest convenience.\n\nWith the latest Automation Builder version (starting with version 2.8.1), the default for \u201cSecurity\u201d is set\nto \u201cIntegrity check\u201d. By keeping this default unchanged, CVE-2025-3394 cannot be exploited.",
"title": "Mitigating factors"
}
],
"publisher": {
"category": "vendor",
"name": "ABB PSIRT",
"namespace": "https://global.abb/group/en/technology/cyber-security/alerts-and-notifications"
},
"references": [
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - PDF version",
"url": "https://search.abb.com/library/Download.aspx?DocumentID=3ADR011407\u0026LanguageCode=en\u0026DocumentPartId=\u0026Action=Launch"
},
{
"category": "self",
"summary": "ABB CYBERSECURITY ADVISORY - CSAF version",
"url": "https://psirt.abb.com/csaf/2025/3adr011407.json"
}
],
"title": "ABB Automation Builder Vulnerabilities in user management and access control",
"tracking": {
"current_release_date": "2025-07-25T00:00:00.000Z",
"generator": {
"date": "2025-09-23T12:06:25.150Z",
"engine": {
"name": "Secvisogram",
"version": "2.5.35"
}
},
"id": "3ADR011407",
"initial_release_date": "2025-04-30T00:00:00.000Z",
"revision_history": [
{
"date": "2025-04-30T00:00:00.000Z",
"legacy_version": "A",
"number": "1",
"summary": "Initial Version"
},
{
"date": "2025-07-25T00:00:00.000Z",
"legacy_version": "B",
"number": "2",
"summary": "Final"
}
],
"status": "final",
"version": "2"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c=2.8.0",
"product": {
"name": "All ABB Automation Builder \u003c= 2.8.0",
"product_id": "AV1"
}
},
{
"category": "product_version",
"name": "2.8.1",
"product": {
"name": "ABB Automation Builder version \u003e=2.8.1",
"product_id": "FX1"
}
}
],
"category": "product_name",
"name": "Automation Builder"
}
],
"category": "vendor",
"name": "ABB"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2025-3394",
"cwe": {
"id": "CWE-732",
"name": "Incorrect Permission Assignment for Critical Resource"
},
"notes": [
{
"category": "description",
"text": "Automation Builder stores all user management information in the project file. Despite fully encrypted\npassword data, an attacker could try to modify parts of the Automation Builder project file by specially\ncrafted contents so that the user management will be overruled.\n",
"title": "CVE Description"
}
],
"product_status": {
"fixed": [
"FX1"
],
"known_affected": [
"AV1"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2025-3394:",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3394"
}
],
"remediations": [
{
"category": "workaround",
"details": "Immediate workarounds to close the vulnerability:\n\n\u2022 CVE-2025-3394: In the project settings, set \u201cSecurity\u201d to \u201cIntegrity check\u201d\n\nABB recommends that customers apply the workarounds at earliest convenience.\nWith the next Automation Builder version 2.8.1, the default for \u201cSecurity\u201d will be set to \u201cIntegrity check\u201d.\nThe release of Automation Builder version 2.8.1 is scheduled for July 2025.",
"product_ids": [
"AV1"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalScore": 7.8,
"environmentalSeverity": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"temporalScore": 7.8,
"temporalSeverity": "HIGH",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"products": [
"AV1"
]
}
],
"title": "CVE-2025-3394"
},
{
"cve": "CVE-2025-3395",
"cwe": {
"id": "CWE-732",
"name": "Incorrect Permission Assignment for Critical Resource"
},
"notes": [
{
"category": "description",
"text": "Automation Builder projects including AC500 V2 or SM560-S devices contain the application files for\nthese devices. An attacker could try to modify parts of these files so that the project can be changed by\noverruling the Automation Builder user management.\n",
"title": "CVE Description"
}
],
"product_status": {
"fixed": [
"FX1"
],
"known_affected": [
"AV1"
]
},
"references": [
{
"category": "external",
"summary": "NVD - CVE-2025-3395",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-3395"
}
],
"remediations": [
{
"category": "workaround",
"details": "Immediate workarounds to close the vulnerability:\n\n\u2022 CVE-2025-3395: In the project settings, set \u201cSecurity\u201d to \u201cEncryption\u201d\n\nABB recommends that customers apply the workarounds at earliest convenience.\nWith the next Automation Builder version 2.8.1, the default for \u201cSecurity\u201d will be set to \u201cIntegrity check\u201d.\nThe release of Automation Builder version 2.8.1 is scheduled for July 2025.",
"product_ids": [
"AV1"
]
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 7.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalScore": 7.1,
"environmentalSeverity": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"temporalScore": 7.1,
"temporalSeverity": "HIGH",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"products": [
"AV1"
]
}
],
"title": "CVE-2025-3395"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
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…