dbcve.org
Epas Gtw FirmwareOperating system · Schneider Electric

CVE-2020-25178

HIGH · 8.8 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
ISaGRAF Workbench communicates with Rockwell Automation ISaGRAF Runtime Versions 4.x and 5.x using TCP/IP. This communication protocol provides various file system operations, as well as the uploading of applications. Data is transferred over this protocol unencrypted, which could allow a remote unauthenticated attacker to upload, read, and delete files.

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 confidence

ISaGRAF Workbench communicates with Rockwell Automation ISaGRAF Runtime Versions 4.x and 5.x over an unencrypted TCP/IP protocol that exposes file system operations including file upload, read, and delete capabilities. A remote unauthenticated attacker can exploit this to manipulate files on the target system due to the complete absence of encryption and authentication in the communication protocol.

MitigationIsolate ISaGRAF Runtime on a dedicated network segment protected by firewall rules restricting access to trusted hosts only, or implement VPN tunneling for encrypted communication; also contact vendor for potential patches addressing the insecure protocol.

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
Affected:= 6.4
Easergy T300 FirmwareOperating system
Affected:<= 2.7.1
Easergy C5 FirmwareOperating system
Affected:< 1.1.0
Micom C264 FirmwareOperating system
Affected:< d6.1
Pacis Gtw FirmwareOperating system
Affected:= 5.1= 5.2= 6.1= 6.3
Saitel Dp FirmwareOperating system
Affected:<= 11.06.21
Saitel Dr FirmwareOperating system
Affected:<= 11.06.12
Scd2200 FirmwareOperating system
Affected:<= 10024

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ISaGRAF Runtime process
    Check running processes for ISaGRAF-related services (isarun.exe, ISaGRAF Runtime service, or similar). On Windows, use Task Manager or 'tasklist /svc' command. On Linux, check for isagraf processes.
    Affected if ISaGRAF Runtime process is found running on the system
  2. Determine Schneider Electric device firmware version
    Access the device web interface, console, or check system information pages for the firmware version. Common paths: Device Info or About section in web UI, or use SNMP/CLI commands like 'show version' or 'sysinfo'. Compare against affected versions: Epas Gtw = 6.4, Easergy T300 <= 2.7.1, Easergy C5 < 1.1.0, Micom C264 < d6.1, Pacis Gtw = 5.1/5.2/6.1/6.3, Saitel Dp <= 11.06.21, Saitel Dr <= 11.06.12, Scd2200 <= 10024.
    Affected if Firmware version matches any of the affected versions listed
  3. Verify ISaGRAF TCP port exposure
    Check if ISaGRAF Runtime port (default TCP 1235, or configured port) is listening and accessible. Use 'netstat -an | grep 1235' or port scanner (nmap -p 1235 <target>) from an external perspective. Check firewall rules to determine if port is exposed to untrusted networks.
    Affected if ISaGRAF TCP port is listening and accessible from an untrusted network segment
  4. Check for encryption on ISaGRAF communication
    Capture network traffic on the ISaGRAF port (tcpdump or Wireshark). Verify if traffic is encrypted (TLS/SSL) or plaintext. ISaGRAF protocol typically sends data in clear text when unencrypted.
    Affected if Network capture shows plaintext/unencrypted ISaGRAF protocol traffic

A system is affected if it runs ISaGRAF Runtime with an unencrypted protocol exposed to the network AND matches one of the listed firmware versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.1.0 or later
Fixed in 1.1.0
Interim mitigation

Isolate ISaGRAF Runtime on a dedicated network segment protected by firewall rules restricting access to trusted hosts only, or implement VPN tunneling for encrypted communication; also contact vendor for potential patches addressing the insecure protocol.

Fix this in Epas Gtw Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-25178 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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