# CVE-2021-22741: Weak cryptography in ClearSCADA (all versions), EcoStruxure Geo SCADA Expert 2019 (all versions), and EcoStruxure Geo SCADA Expert 2020 (V83.7742.1 and prior)

> Weak password hashing in ClearSCADA and Geo SCADA Expert allows attackers with database file access to decrypt user credentials.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gqjp-r446-ff55

## What is CVE-2021-22741?

CVE-2021-22741 is a medium-severity vulnerability in ClearSCADA (all versions), EcoStruxure Geo SCADA Expert 2019 (all versions), and EcoStruxure Geo SCADA Expert 2020 (V83.7742.1 and prior), published on 26 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use of Password Hash with Insufficient Computational Effort vulnerability exists in ClearSCADA (all versions), EcoStruxure Geo SCADA Expert 2019 (all versions), and EcoStruxure Geo SCADA Expert 2020 (V83.7742.1 and prior), which could cause the revealing of account credentials when server database files are available. Exposure of these files to an attacker can make the system vulnerable to password decryption attacks. Note that “.sde” configuration export files do not contain user account password hashes.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2021-22741?

It affects 3 products.


Products: Schneider-Electric Clearscada, Schneider-Electric Ecostruxure Geo Scada Expert 2019, Schneider-Electric Ecostruxure Geo Scada Expert 2020.

## How do I fix CVE-2021-22741?

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

## Is CVE-2021-22741 being exploited?

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

## Other vulnerabilities in ClearSCADA (all versions), EcoStruxure Geo SCADA Expert 2019 (all versions), and EcoStruxure Geo SCADA Expert 2020 (V83.7742.1 and prior)

- [CVE-2019-6854](https://insights.sbomify.com/CVE-2019-6854/): Missing authorization in EcoStruxure Geo SCADA Expert (ClearSCADA) with initial releases before 1 January 2019 (see notification for more details) (high 7.8)
- [CVE-2022-24318](https://insights.sbomify.com/CVE-2022-24318/): Weak cryptography in ClearSCADA (All Versions), EcoStruxure Geo SCADA Expert 2019 (All Versions), EcoStruxure Geo SCADA Expert 2020 (All Versions) (high 7.5)
- [CVE-2022-24321](https://insights.sbomify.com/CVE-2022-24321/): Denial of service in ClearSCADA (All Versions), EcoStruxure Geo SCADA Expert 2019 (All Versions), EcoStruxure Geo SCADA Expert 2020 (All Versions) (high 7.5)
- [CVE-2022-24319](https://insights.sbomify.com/CVE-2022-24319/): Other in ClearSCADA (All Versions), EcoStruxure Geo SCADA Expert 2019 (All Versions), EcoStruxure Geo SCADA Expert 2020 (All Versions) (medium 5.9)
- [CVE-2022-24320](https://insights.sbomify.com/CVE-2022-24320/): Other in ClearSCADA (All Versions), EcoStruxure Geo SCADA Expert 2019 (All Versions), EcoStruxure Geo SCADA Expert 2020 (All Versions) (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22741 and fix it if it is affected.

What it is: CVE-2021-22741 is a medium-severity vulnerability in ClearSCADA (all versions), EcoStruxure Geo SCADA Expert 2019 (all versions), and EcoStruxure Geo SCADA Expert 2020 (V83.7742.1 and prior), published on 26 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22741 in the wild and no public exploit code.

Affected product: ClearSCADA (all versions), EcoStruxure Geo SCADA Expert 2019 (all versions), and EcoStruxure Geo SCADA Expert 2020 (V83.7742.1 and prior). 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-2021-22741/ (Markdown: https://insights.sbomify.com/CVE-2021-22741/index.md)
```

## Sources

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

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