# CVE-2020-25180: Rockwell Automation ISaGRAF5 Runtime Use of Hard-coded Cryptographic Key

> Remote attackers can bypass authentication using a hard-coded cryptographic key to access privileged commands and disclose information on ISaGRAF Runtime devices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Mar 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-rq23-5rjf-c828

## What is CVE-2020-25180?

CVE-2020-25180 is a medium-severity vulnerability in Rockwell Automation ISaGRAF Runtime, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2020-25180?

It affects 17 products.


Products: Rockwellautomation Aadvance Controller, Rockwellautomation Isagraf Free Runtime, Rockwellautomation Isagraf Runtime, Rockwellautomation Micro810 Firmware, Rockwellautomation Micro820 Firmware, Rockwellautomation Micro830 Firmware, Rockwellautomation Micro850 Firmware, Rockwellautomation Micro870 Firmware, Schneider-Electric Easergy C5 Firmware, Schneider-Electric Easergy T300 Firmware, Schneider-Electric Epas Gtw Firmware, Schneider-Electric Micom C264 Firmware, Schneider-Electric Pacis Gtw Firmware, Schneider-Electric Saitel Dp Firmware, Schneider-Electric Saitel Dr Firmware, Schneider-Electric Scd2200 Firmware, Xylem Multismart Firmware.

## How do I fix CVE-2020-25180?

No fix has been published for CVE-2020-25180 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-25180 being exploited?

There is no known exploitation of CVE-2020-25180 in the wild and no public exploit code.

## Other vulnerabilities in Rockwell Automation ISaGRAF Runtime

- [CVE-2020-25176](https://insights.sbomify.com/CVE-2020-25176/): Rockwell Automation ISaGRAF5 Runtime Relative Path Traversal (critical 9.1)
- [CVE-2020-25184](https://insights.sbomify.com/CVE-2020-25184/): Rockwell Automation ISaGRAF5 Runtime Unprotected Storage of Credentials (high 7.8)
- [CVE-2020-25178](https://insights.sbomify.com/CVE-2020-25178/): Rockwell Automation ISaGRAF5 Runtime Cleartext Transmission of Sensitive Information (high 7.5)
- [CVE-2020-25182](https://insights.sbomify.com/CVE-2020-25182/): Rockwell Automation ISaGRAF5 Runtime Uncontrolled Search Path Element (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25180 and fix it if it is affected.

What it is: CVE-2020-25180 is a medium-severity vulnerability in Rockwell Automation ISaGRAF Runtime, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-25180 in the wild and no public exploit code.

Affected product: Rockwell Automation ISaGRAF Runtime. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25180/ (Markdown: https://insights.sbomify.com/CVE-2020-25180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25180
- OSV: https://osv.dev/vulnerability/CVE-2020-25180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25180/
Summaries are generated and may contain mistakes; the official description above is the record.