CVE-2025-3394
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect Permission Assignment for Critical Resource vulnerability in ABB Automation Builder.This issue affects Automation Builder: through 2.8.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn incorrect permission assignment vulnerability exists in ABB Automation Builder through version 2.8.0, where critical resources (likely files, directories, or system objects) have been configured with overly permissive access controls. This could allow a local attacker to read, modify, or execute sensitive resources they should not have access to, potentially leading to privilege escalation or system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify ABB Automation Builder installation existsCheck for the presence of ABB Automation Builder by looking in typical installation directories (e.g., C:\Program Files\ABB\AutomationBuilder or C:\Program Files (x86)\ABB\AutomationBuilder) or by checking the Windows registry under HKLM\SOFTWARE\ABB\AutomationBuilder or HKLM\SOFTWARE\WOW6432Node\ABB\AutomationBuilderAffected if The software is found installed on the system
-
Determine installed versionLocate the version information - check the registry key for the installed version (e.g., under the registry path found above, look for a 'Version' or 'ProductVersion' value), or check the 'About' or version info within the application's executable or dll files in the installation directoryAffected if The version is 2.8.0 or lower, or if a version cannot be determined but the product is present
-
Identify installation directory permissionsUse icacls command on the ABB Automation Builder installation directory (e.g., icacls "C:\Program Files\ABB\AutomationBuilder") to list all access control entries, noting users/groups with access rightsAffected if Permissions grant Read, Write, or Execute access to untrusted users or groups such as Everyone, Users (for writable), or authenticated users without proper restriction
-
Check critical resource permissionsUse icacls on subdirectories and critical files within the installation (e.g., icacls "C:\Program Files\ABB\AutomationBuilder\*" /T) to identify files or folders with overly permissive ACLs - look for entries like (A;) indicating Allow permissions to broad groupsAffected if Critical configuration files, scripts, executables, or data directories grant access to Everyone, Users, or other unprivileged groups with Modify or Full Control permissions
A system is affected if ABB Automation Builder version 2.8.0 or lower is installed AND critical files or directories within the installation have permissions that allow untrusted users or groups (such as Everyone, Users with write access, or similar) to read, modify, or execute sensitive resources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate ABB Automation Builder to a version beyond 2.8.0 once available, or review and correct file system or registry permissions on critical resources to enforce least-privilege access controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3394 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3394 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data