dbcve.org
Epas Gtw FirmwareOperating system · Schneider Electric

CVE-2020-25180

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Rockwell Automation ISaGRAF Runtime Versions 4.x and 5.x includes the functionality of setting a password that is required to execute privileged commands. The password value passed to ISaGRAF Runtime is the result of encryption performed with a fixed key value using the tiny encryption algorithm (TEA) on an entered or saved password. A remote, unauthenticated attacker could pass their own encrypted password to the ISaGRAF 5 Runtime, which may result in information disclosure on the device.

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 confidence

The ISaGRAF Runtime uses TEA (tiny encryption algorithm) with a fixed key to encrypt passwords. A remote, unauthenticated attacker can bypass authentication by submitting their own TEA-encrypted password value, allowing execution of privileged commands and information disclosure.

MitigationReplace reversible TEA encryption with proper password hashing (e.g., bcrypt, Argon2) or implement per-instance random encryption keys with secure key management. Consider network segmentation and disabling remote access if not required.

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
None
Availability
None

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

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

  1. Identify the Schneider Electric device model
    Locate the device nameplate or check the system documentation to confirm the exact model (Epas Gtw, Easergy T300, Easergy C5, Micom C264, Pacis Gtw, Saitel Dp, Saitel Dr, or Scd2200)
    Affected if The device model matches one of the affected products listed in the CVE
  2. Check the installed firmware version
    Access the device's web interface, console, or firmware management system and retrieve the current firmware version number
    Affected if The firmware version falls within the affected ranges: 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, or 6.3; Saitel Dp <= 11.06.21; Saitel Dr <= 11.06.12; Scd2200 <= 10024
  3. Verify if ISaGRAF Runtime is installed and running
    Check the device's running processes, services, or installed software list for the ISaGRAF Runtime component
    Affected if ISaGRAF Runtime is present on the device
  4. Confirm network accessibility of the authentication interface
    Check network configuration to determine if the device's management interface or authentication service is exposed to network access (local or remote)
    Affected if The authentication interface is accessible over the network (LAN or WAN)
  5. Inspect for TEA-encrypted password storage
    Review configuration files, password databases, or credential storage on the device for evidence of TEA-encrypted passwords rather than hashed passwords
    Affected if Passwords are stored using TEA encryption with a fixed key rather than secure hashing

A user is affected if they operate any of the listed Schneider Electric firmware versions with ISaGRAF Runtime enabled and the authentication interface is network-accessible.

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

Replace reversible TEA encryption with proper password hashing (e.g., bcrypt, Argon2) or implement per-instance random encryption keys with secure key management. Consider network segmentation and disabling remote access if not required.

Fix this in Epas Gtw Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25180 — 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-25180 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