Skip to content
Fencer Intel
medium 4.3

CVE-2012-3037 json

The Siemens SIMATIC S7-1200 2.x PLC does not properly protect the private key of the SIMATIC CONTROLLER Certification Authority certificate…

published 14y ago modified 4mo ago also EUVD-2012-3015

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

The Siemens SIMATIC S7-1200 2.x PLC does not properly protect the private key of the SIMATIC CONTROLLER Certification Authority certificate, which allows remote attackers to spoof the S7-1200 web server by using this key to create a forged certificate.

Patch / fix

  • siemens simatic_s7-1200_firmware 3.0.0
  • siemens simatic_s7-1200_cpu_1211c_firmware 3.0.0
  • siemens simatic_s7-1200_cpu_1212c_firmware 3.0.0
  • siemens simatic_s7-1200_cpu_1212fc_firmware 3.0.0
  • siemens simatic_s7-1200_cpu_1214_fc_firmware 3.0.0
  • siemens simatic_s7-1200_cpu_1214c_firmware 3.0.0
  • siemens simatic_s7-1200_cpu_1215_fc_firmware 3.0.0
  • siemens simatic_s7-1200_cpu_1215c_firmware 3.0.0
  • siemens simatic_s7-1200_cpu_1217c_firmware 3.0.0

Is CVE-2012-3037 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-12-263-01 updated cvss 9.3

Siemens S7-1200 Insecure Storage of HTTPS CA Certificate

  • Siemens SIMATIC S7-1200 V2.x
    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.47% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-295 Improper Certificate Validation

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.