Epas Gtw FirmwareOperating system · Schneider Electric
CVE-2020-25182
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 searches for and loads DLLs as dynamic libraries. Uncontrolled loading of dynamic libraries could allow a local, unauthenticated attacker to execute arbitrary code. This vulnerability only affects ISaGRAF Runtime when running on Microsoft Windows systems.
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 confidenceISaGRAF Runtime searches for and loads DLLs from unspecified paths without proper validation, allowing a local unauthenticated attacker to place a malicious DLL in a location where the application will load it, leading to arbitrary code execution on Windows systems.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Identify ISaGRAF Runtime installationSearch for the ISaGRAF Runtime executable (typically isa7rt.exe or similar) in common installation directories such as C:\Program Files\ISaGRAF or C:\ISAAffected if ISaGRAF Runtime executable is found on the system
-
Confirm firmware version for Schneider Electric Epas GtwCheck the firmware version reported in the device management interface or system information (typically equals 6.4 for affected versions)Affected if Firmware version equals 6.4
-
Confirm firmware version for Schneider Electric Easergy T300Check the firmware version reported in the device management interface or system information (versions <= 2.7.1 are affected)Affected if Firmware version is 2.7.1 or lower
-
Confirm firmware version for Schneider Electric Easergy C5Check the firmware version reported in the device management interface or system information (versions < 1.1.0 are affected)Affected if Firmware version is below 1.1.0
-
Confirm firmware version for Schneider Electric Micom C264Check the firmware version reported in the device management interface or system information (versions < d6.1 are affected)Affected if Firmware version is below d6.1
-
Verify file system permissions on application directoriesInspect file system permissions on directories where ISaGRAF Runtime is installed. Check if non-privileged users have write access to directories in the DLL search path (the application directory, system PATH directories, or Windows system directories)Affected if Non-privileged users have write permissions to directories from which ISaGRAF loads DLLs
The system is affected if it runs ISaGRAF Runtime on any of the listed Schneider Electric firmware versions AND non-privileged users can write to directories in the application's DLL search path.
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
Restrict file system permissions to prevent unauthorized users from writing to directories in the DLL search path; verify if vendor has released a patch for secure DLL loading.
Fix this in Epas Gtw Firmware
Scoped from the published advisory
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25182 — 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-25182 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