CVE-2025-0477
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 · uneditedAn encryption vulnerability exists in all versions prior to V15.00.001 of Rockwell Automation FactoryTalk® AssetCentre. The vulnerability exists due to a weak encryption methodology and could allow a threat actor to extract passwords belonging to other users of the application.
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 · high confidenceFactoryTalk AssetCentre versions prior to V15.00.001 contain a weak encryption vulnerability that allows threat actors to extract user passwords from the application. The weak encryption methodology exposes credential data stored by the system.
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< 15.00.01CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 FactoryTalk AssetCentre installationCheck for FactoryTalk AssetCentre in the Windows Programs and Features list (appwiz.cpl) or look for the installation directory under C:\Program Files\Rockwell Software\FactoryTalk AssetCentreAffected if FactoryTalk AssetCentre is not found on the system, the vulnerability does not apply
-
Locate the installed versionOpen the Windows Registry and navigate to HKLM\SOFTWARE\Rockwell Software\FactoryTalk AssetCentre\Info, or right-click the FactoryTalk AssetCentre application shortcut and view Properties to find the version informationAffected if No version information is available or the version cannot be determined, treat as potentially affected
-
Compare version against affected rangeCompare the installed version number to the affected range: any version prior to V15.00.001 (or 15.00.01). Common version formats include values like 14.0, 14.0.1, 15.0, or 14.00.00Affected if The installed version is lower than 15.00.001 (for example, 14.x, 13.x, or any build prior to the V15.00.001 release)
-
Check for password storage filesFactoryTalk AssetCentre stores user credentials in its database or configuration files. Locate the data directory under the installation path (typically C:\Program Files\Rockwell Software\FactoryTalk AssetCentre\Data or within a SQL Server database used by the application)Affected if The application uses its default internal database or file-based credential storage, and the version is affected, then weak encryption could allow password extraction
The environment is affected if FactoryTalk AssetCentre is installed and the installed version is any release prior to V15.00.001 (15.00.01).
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.
dbcve · scoped15.00.01
Upgrade FactoryTalk AssetCentre to version V15.00.001 or later to remediate the weak encryption vulnerability. Review user account credentials that may have been compromised and consider password resets.
FactoryTalk AssetCentre V15.00.001
- 1. Back up the current FactoryTalk AssetCentre database and configuration files before proceeding with any upgrade.
- 2. Download the FactoryTalk AssetCentre V15.00.001 (or later) update from the Rockwell Automation Download Center at https://www.rockwellautomation.com/ or your local support portal.
- 3. Stop all FactoryTalk AssetCentre services on the server before applying the update.
- 4. Install the V15.00.001 update following the Rockwell Automation installation instructions provided with the download.
- 5. After installation, verify that all FactoryTalk AssetCentre services start successfully.
- 6. As a precaution due to the credential exposure vulnerability, consider forcing password resets for all users who accessed the affected system, especially those with administrative privileges.
- 7. Review application logs for any suspicious activity that may have occurred before the patch was applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0477 — 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-0477 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