LiveActive security incident?Get immediate response
CVE Record

CVE-2014-5413: Schneider Electric SCADA Expert ClearSCADA Cryptographic Issues

Schneider Electric StruxureWare SCADA Expert ClearSCADA 2010 R3 through 2014 R1 uses the MD5 algorithm for an X.509 certificate, which makes it easier for remote attackers to spoof servers via a cryptographic attack against this algorithm.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects older Schneider Electric ClearSCADA and SCADA Expert ClearSCADA versions that used MD5 in an X.509 certificate. MD5 is weak, so an attacker could have an easier path to impersonating a server. The business risk is trust failure in SCADA communications, not system takeover by itself.

Executive priority

Handle as a moderate-priority industrial control risk. It is old and not KEV-listed in the supplied evidence, but remaining affected deployments could undermine trusted SCADA communications and should be remediated through vendor-approved maintenance planning.

Technical view

CVE-2014-5413 is a cryptographic weakness in specified ClearSCADA releases from 2010 R3 through 2014 R1.1. The CVSS v2 vector is network reachable, low complexity, unauthenticated, with partial confidentiality and integrity impact. The reported issue is MD5 use in an X.509 certificate, enabling server spoofing through cryptographic attack.

Likely exposure

Exposure is most likely in organizations still operating the listed Schneider Electric ClearSCADA or SCADA Expert ClearSCADA builds, especially where clients trust affected server certificates across routable or remote-access networks.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation. The plausible attack context is server impersonation against SCADA communications where certificate trust depends on MD5-signed material. Evidence provided does not support claims of public exploit use.

Researcher notes

The source bundle identifies affected versions and the cryptographic condition but does not include patch details or exploit telemetry. Avoid overstating impact beyond server spoofing with partial confidentiality and integrity impact under CVSS v2.

Mitigation direction

  • Inventory ClearSCADA and SCADA Expert ClearSCADA versions against the affected build list.
  • Check Schneider Electric and CISA advisory guidance for supported remediation steps.
  • Prioritize removing MD5-based certificate trust where vendor guidance allows.
  • Limit untrusted network access to affected SCADA services pending remediation.
  • Treat certificate changes as operational changes requiring SCADA owner approval.

Validation and detection

  • Confirm product name, version, and build on each ClearSCADA server.
  • Review certificate algorithms in the affected deployment for MD5 use.
  • Verify remote access paths that could reach affected SCADA services.
  • Check whether vendor remediation guidance has been applied and documented.
  • Record compensating controls if affected systems cannot be upgraded immediately.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-310: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-5413 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:N/C:P/I:P/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 2.0MediumAV:N/AC:L/Au:N/C:P/I:P/A:N104.9Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

6.4Medium
CVSS 2.0 vector shape for CVE-2014-5413Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:N/C:P/I:P/A:N

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Schneider ElectricClearSCADA2010 R3 (build 72.4560), 2010 R3.1 (build 72.4644), 2010 R3.2unaffected
Schneider ElectricSCADA Expert ClearSCADA2013 R1 (build 73.4729), 2013 R1.1 (build 73.4832), 2013 R1.1a (build 73.4903), 2013 R1.2 (build 73.4955), 2013 R2 (build 74.5094), 2013 R2.1 (build 74.5192), 2014 R1 (build 75.5210), 2014 R1.1unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-310 · source CWE mapping

Cryptographic Issues

Cryptographic Issues represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.