dbcve.org
ClearscadaApplication · Schneider Electric

CVE-2023-0595

MEDIUM · 5.3 CVSS v3.1 Published 2023-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a log injection vulnerability (CWE-117) in EcoStruxure Geo SCADA and ClearSCADA products. When malicious packets are sent to the database web port (default 443), the application fails to properly neutralize special characters in the input before writing to log files, allowing attackers to inject fake log entries that could be misinterpreted by log analysis tools or security personnel.

MitigationUpdate to versions released October 2022 or later which contain the fix. Additionally, network segmentation and firewall rules can limit exposure to the database web port (443).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ClearscadaApplication
Affected:all versions
Ecostruxure Geo Scada Expert 2019Application
Affected:all versions= 81.7268.1= 81.7322.1= 81.7429.2= 81.7457.1= 81.7488.1= 81.7522.1= 81.7545.1= 81.7578.1= 81.7613.1= 81.7641.1= 81.7690.1
Ecostruxure Geo Scada Expert 2020Application
Affected:all versions= 83.7551.1= 83.7578.1= 83.7613.1= 83.7641.1= 83.7692.1= 83.7717.1= 83.7742.1= 83.7787.1= 83.7809.1= 83.7840.1= 83.7875.1
Ecostruxure Geo Scada Expert 2021Application
Affected:all versions= 84.8027.1= 84.8108.1= 84.8120.1= 84.8158.1= 84.8182.1= 84.8197.1= 84.8218.1= 84.8269.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Geo SCADA or ClearSCADA version
    Check the Windows Programs and Features list or the installation directory for version information. The product typically installs under 'Schneider Electric' in the program menu.
    Affected if The installed version matches any of the listed affected versions (all versions of ClearSCADA; all versions of Geo SCADA Expert 2019/2020/2021; or any of the specific build numbers 81.x, 83.x, or 84.x cited).
  2. Verify the database web port is accessible
    Test TCP connectivity to port 443 (or the configured SSL port) on the server where the SCADA application is running using telnet, nc, or PowerShell Test-NetConnection.
    Affected if Port 443 is open and accepting connections from untrusted network segments, indicating potential exposure to external attackers.
  3. Examine application logs for suspicious entries
    Navigate to the ClearSCADA or Geo SCADA log directory (typically in the installation folder or C:\ProgramData\Schneider Electric\ClearSCADA\Logs) and review recent log files for unusual patterns, especially entries containing line breaks, timestamps from unusual sources, or repeated authentication attempts with special characters.
    Affected if Logs contain entries with embedded newline characters, unexpected formatting, or entries that appear to be injected rather than generated by normal system processes.
  4. Check if the installed version predates the October 2022 patch
    Compare the installed version and build number against the fixed releases. If the version/build is earlier than the October 2022 releases, it is likely vulnerable.
    Affected if The installed version is older than the October 2022 patch releases and matches any of the affected version ranges.

A system is affected if it runs any version of ClearSCADA or Geo SCADA Expert (2019/2020/2021) and has the database web port (443) accessible from a network where malicious packets could be sent.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to versions released October 2022 or later which contain the fix. Additionally, network segmentation and firewall rules can limit exposure to the database web port (443).

Fix this in Clearscada Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0595 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0595 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data