# CVE-2020-28219: Information disclosure in EcoStruxure Geo SCADA Expert 2019 (Original release and Monthly Updates to September 2020, from 81.7268.1 to 81.7578.1) and EcoStruxure Geo SCADA Expert 2020 (Original release and Monthly Updates to September 2020, from 83.7551.1 to 83.7578.1)

> Insufficiently protected credentials in EcoStruxure Geo SCADA Expert allow exposure of server-side user credentials to web users.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-prq6-5cg3-rr76

## What is CVE-2020-28219?

CVE-2020-28219 is a high-severity vulnerability in EcoStruxure Geo SCADA Expert 2019 (Original release and Monthly Updates to September 2020, from 81.7268.1 to 81.7578.1) and EcoStruxure Geo SCADA Expert 2020 (Original release and Monthly Updates to September 2020, from 83.7551.1 to 83.7578.1), published on 11 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A CWE-522: Insufficiently Protected Credentials vulnerability exists in EcoStruxure Geo SCADA Expert 2019 (Original release and Monthly Updates to September 2020, from 81.7268.1 to 81.7578.1) and EcoStruxure Geo SCADA Expert 2020 (Original release and Monthly Updates to September 2020, from 83.7551.1 to 83.7578.1), that could cause exposure of credentials to server-side users when web users are logged in to Virtual ViewX.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 2 products.


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

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

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

## Is CVE-2020-28219 being exploited?

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

## Other vulnerabilities in EcoStruxure Geo SCADA Expert 2019 (Original release and Monthly Updates to September 2020, from 81.7268.1 to 81.7578.1) and EcoStruxure Geo SCADA Expert 2020 (Original release and Monthly Updates to September 2020, from 83.7551.1 to 83.7578.1)

- [CVE-2023-22610](https://insights.sbomify.com/CVE-2023-22610/): Missing authorization in EcoStruxure Geo SCADA Expert 2019 - 2021 (formerly known as ClearSCADA) (critical 9.1)
- [CVE-2023-22611](https://insights.sbomify.com/CVE-2023-22611/): Information disclosure in EcoStruxure Geo SCADA Expert 2019 - 2021 (formerly known as ClearSCADA) (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28219 is a high-severity vulnerability in EcoStruxure Geo SCADA Expert 2019 (Original release and Monthly Updates to September 2020, from 81.7268.1 to 81.7578.1) and EcoStruxure Geo SCADA Expert 2020 (Original release and Monthly Updates to September 2020, from 83.7551.1 to 83.7578.1), published on 11 Dec 2020. 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-2020-28219 in the wild and no public exploit code.

Affected product: EcoStruxure Geo SCADA Expert 2019 (Original release and Monthly Updates to September 2020, from 81.7268.1 to 81.7578.1) and EcoStruxure Geo SCADA Expert 2020 (Original release and Monthly Updates to September 2020, from 83.7551.1 to 83.7578.1). 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-28219/ (Markdown: https://insights.sbomify.com/CVE-2020-28219/index.md)
```

## Sources

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

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