CVE-2025-3395
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, Cleartext Storage of Sensitive Information 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 confidenceABB Automation Builder through version 2.8.0 contains two related vulnerabilities: incorrect permission assignment allows unauthorized access to critical resources, and sensitive information is stored in cleartext without encryption. This could allow local attackers with file system access to read sensitive data or modify critical resources due to overly permissive access controls.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Check ABB Automation Builder installed versionLocate and inspect the Automation Builder installation directory, or use the application's 'About' or 'Help > Version' menu to identify the exact version number installed.Affected if The installed version is 2.8.0 or any earlier version.
-
Identify configuration and project data directoriesLocate the default installation path (commonly under Program Files/ABB or within user profile directories) and identify folders containing configuration files, project data, credentials, keys, or other sensitive resources.Affected if Configuration, project, or sensitive data directories exist on the system.
-
Inspect file system permissions on sensitive directoriesRight-click each identified sensitive directory, select Properties > Security, and review the granted permissions. Check if unauthorized users or groups (such as Users, Everyone, or low-privilege accounts) have Read, Write, or Modify access.Affected if Any non-administrator user or group has Read, Write, or Modify permissions on configuration or sensitive data directories.
-
Examine configuration files for cleartext sensitive dataOpen configuration files (such as .xml, .ini, .cfg, .config, or proprietary file formats) within the identified directories using a text editor. Search for patterns indicating credentials, passwords, keys, tokens, or other secrets.Affected if Any credentials, passwords, keys, tokens, or other sensitive data are stored in plain text without encryption or encoding.
A user is affected if ABB Automation Builder version 2.8.0 or earlier is installed AND sensitive configuration files have overly permissive access controls OR sensitive data is stored in cleartext.
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 dataReview and restrict file system permissions on configuration files, project data, and sensitive resources. Implement encryption for any stored sensitive information such as credentials, keys, or configuration data.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3395 — 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-3395 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