CVE-2014-0755
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 · uneditedRockwell Automation RSLogix 5000 7 through 20.01, and 21.0, does not properly implement password protection for .ACD files (aka project files), which allows local users to obtain sensitive information or modify data via unspecified vectors.
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 confidenceRockwell Automation RSLogix 5000 versions 7 through 20.01 and 21.0 fail to properly enforce password protection on .ACD project files, allowing local authenticated users to bypass security controls and access sensitive configuration data or modify project contents without proper authorization.
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= 7.0= 18.0= 20.01= 21.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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
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.
-
Identify installed RSLogix 5000 versionCheck the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Rockwell Software\RSLogix 5000\InstallDir or look in Program Files for RSLogix 5000 folder and check version infoAffected if Installed version is 7.x, 18.x, 20.01, or 21.0, or any version from 7.0 through 20.01 or version 21.0
-
Locate .ACD project files on the systemSearch file system for .ACD file extension in typical project directories such as C:\RSLogix\Projects, C:\Users\%username%\Documents\RSLogix 5000, or shared network drivesAffected if Any .ACD project files exist on the system
-
Test password protection enforcement on .ACD filesAttempt to open an .ACD file using RSLogix 5000 without providing a password, or check if the file can be accessed by third-party hex editors or text editors to read contentsAffected if The .ACD file contents can be read or modified without requiring password authentication through RSLogix 5000
-
Verify file-level access controls on .ACD filesRight-click an .ACD file, select Properties, and check the Security tab to see if authenticated local users can access the file without proper authorizationAffected if Local authenticated users who should not have access can still read or modify the .ACD file due to weak file system permissions
If RSLogix 5000 version 7.0 through 20.01 or 21.0 is installed and .ACD project files exist that can be accessed or modified without proper password authentication, the environment is affected by this vulnerability.
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 dataUpgrade RSLogix 5000 to a patched version and re-secured project files with strong passwords; implement additional file system access controls to limit exposure of .ACD files to authorized personnel only.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0755 — 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-2014-0755 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