# CVE-2019-6854: Missing authorization in EcoStruxure Geo SCADA Expert (ClearSCADA) with initial releases before 1 January 2019 (see notification for more details)

> Low-privilege users with file system access can delete or modify critical database, setting, or certificate files in EcoStruxure Geo SCADA Expert.

- **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:** 6 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hwwq-6fg7-74h6

## What is CVE-2019-6854?

CVE-2019-6854 is a high-severity missing authorization vulnerability in EcoStruxure Geo SCADA Expert (ClearSCADA) with initial releases before 1 January 2019 (see notification for more details), published on 6 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A CWE-287: Improper Authentication vulnerability exists in a folder within EcoStruxure Geo SCADA Expert (ClearSCADA) -with initial releases before 1 January 2019- which could cause a low privilege user to delete or modify database, setting or certificate files. Those users must have access to the file system of that operating system to exploit this vulnerability. Affected versions in current support includes ClearSCADA 2017 R3, ClearSCADA 2017 R2, and ClearSCADA 2017.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-6854?

It affects 1 product.


Products: Schneider-Electric Clearscada.

## How do I fix CVE-2019-6854?

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

## Is CVE-2019-6854 being exploited?

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

## Other vulnerabilities in EcoStruxure Geo SCADA Expert (ClearSCADA) with initial releases before 1 January 2019 (see notification for more details)

- [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-2021-22741](https://insights.sbomify.com/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) (medium 6.7)
- [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-2019-6854 and fix it if it is affected.

What it is: CVE-2019-6854 is a high-severity missing authorization vulnerability in EcoStruxure Geo SCADA Expert (ClearSCADA) with initial releases before 1 January 2019 (see notification for more details), published on 6 Jan 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-2019-6854 in the wild and no public exploit code.

Affected product: EcoStruxure Geo SCADA Expert (ClearSCADA) with initial releases before 1 January 2019 (see notification for more details). 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-2019-6854/ (Markdown: https://insights.sbomify.com/CVE-2019-6854/index.md)
```

## Sources

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

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