Skip to content
Fencer Intel
medium 6.4

CVE-2014-5413 json

Schneider Electric SCADA Expert ClearSCADA Cryptographic Issues

published 12y ago modified 4mo ago also EUVD-2014-5301

cvss
6.4
version 2.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

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.

Patch / fix

  • Schneider Electric ClearSCADA 2010 R3.2
  • Schneider Electric SCADA Expert ClearSCADA 2014 R1.1

Is CVE-2014-5413 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-14-259-01A updated cvss 4.3

Schneider Electric SCADA Expert ClearSCADA Vulnerabilities (Update A)

  • Schneider Electric ClearSCADA 2010 R3_build_72.4560, R3.1_build_72.4644 Schneider Electric SCADA Expert ClearSCADA 2013 R1_build_73.4729, R1.1_build_73.4832, R1.1a_build_73.4903, R1.2_build_73.4955 Schneider Electric SCADA Expert ClearSCADA 2014 R1_build_75.5210
    affected: mitigation

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

1.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Schneider Electric ClearSCADA
  • Schneider Electric SCADA Expert ClearSCADA

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.