Epas Gtw FirmwareOperating system · Schneider Electric
CVE-2020-25184
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 ISaGRAF Runtime Versions 4.x and 5.x stores the password in plaintext in a file that is in the same directory as the executable file. ISaGRAF Runtime reads the file and saves the data in a variable without any additional modification. A local, unauthenticated attacker could compromise the user passwords, resulting in information disclosure.
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 confidenceRockwell Automation ISaGRAF Runtime versions 4.x and 5.x stores user passwords in plaintext within a file located in the same directory as the executable. The runtime reads this file and loads the password data directly into a variable without any encryption, hashing, or additional processing. A local, unauthenticated attacker with file system access can read this plaintext password file to compromise user credentials.
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
Epas Gtw FirmwareOperating system
= 6.4<= 2.7.1< 1.1.0< d6.1= 5.1= 5.2= 6.1= 6.3<= 11.06.21<= 11.06.12<= 10024CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify ISaGRAF Runtime installationLocate ISaGRAF Runtime installation directory. Check for executable files (isagraf.exe, Runtime.exe, or similar) and identify the installed version from file properties, About dialog, or version info in executable metadata.Affected if Version is 4.x or 5.x (any minor version)
-
Locate password storage fileSearch in the ISaGRAF installation directory for files that may contain user credentials. Common naming patterns include: password.dat, passwd.txt, user.dat, user.txt, or files with .pwd, .dat, .ini extensions that could store authentication data.Affected if A password file exists in the same directory as the ISaGRAF Runtime executable
-
Inspect password file contentsOpen the identified password file using a text editor or hex viewer. Examine whether the contents appear as plaintext readable characters rather than hashed or encrypted data.Affected if Password file contains plaintext passwords or readable credential data without encryption or hashing indicators
-
Verify credential loading mechanismIf available, monitor process memory or examine application logs during ISaGRAF startup to confirm the password file is loaded directly into memory without transformation.Affected if Runtime loads password file contents directly into memory without cryptographic processing
-
Check file system permissionsReview file system permissions on the password file to determine if unauthorized local users can read the file.Affected if File permissions allow read access to non-admin users or the file is accessible without authentication
Environment is affected if ISaGRAF Runtime versions 4.x or 5.x is installed and a plaintext password file exists in the executable directory with weak access controls.
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 data1.1.0
Implement proper password protection by hashing passwords (e.g., using bcrypt, scrypt, or Argon2) with salt before storage, or encrypt the password file using strong encryption with proper key management. Additionally, enforce authentication controls and restrict file system permissions to prevent unauthorized access.
Fix this in Epas Gtw Firmware
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25184 — 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-2020-25184 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