# CVE-2023-0595: Other in ClearSCADA

> Attackers can inject malicious data into logs via network packets, causing misinterpretation of log files in Schneider Electric SCADA systems.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2023
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-27q3-84pw-qmf2

## What is CVE-2023-0595?

CVE-2023-0595 is a medium-severity vulnerability in Schneider Electric ClearSCADA , published on 24 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CWE-117: Improper Output Neutralization for Logs vulnerability exists that could cause the misinterpretation of log files when malicious packets are sent to the Geo SCADA server's database web port (default 443). Affected products: EcoStruxure Geo SCADA Expert 2019, EcoStruxure Geo SCADA Expert 2020, EcoStruxure Geo SCADA Expert 2021(All Versions prior to October 2022), ClearSCADA (All Versions)

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2023-0595?

It affects 4 products.


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

## How do I fix CVE-2023-0595?

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

## Is CVE-2023-0595 being exploited?

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

## Other vulnerabilities in Schneider Electric ClearSCADA 

- [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-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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0595 and fix it if it is affected.

What it is: CVE-2023-0595 is a medium-severity vulnerability in Schneider Electric ClearSCADA , published on 24 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-0595 in the wild and no public exploit code.

Affected product: Schneider Electric ClearSCADA . 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-2023-0595/ (Markdown: https://insights.sbomify.com/CVE-2023-0595/index.md)
```

## Sources

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

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