Skip to content
Fencer Intel
medium 5.0

CVE-2011-4512 json

CRLF injection vulnerability in the HMI web server in Siemens WinCC flexible 2004, 2005, 2007, and 2008 before SP3; WinCC V11 (aka TIA port…

published 2012-02-03 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4438

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

Summary

CRLF injection vulnerability in the HMI web server in Siemens WinCC flexible 2004, 2005, 2007, and 2008 before SP3; WinCC V11 (aka TIA portal) before SP2 Update 1; the TP, OP, MP, Comfort Panels, and Mobile Panels SIMATIC HMI panels; WinCC V11 Runtime Advanced; and WinCC flexible Runtime allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified vectors.

Vendor advisories

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

cisa ICSA-12-030-01A updated cvss 5.0

Siemens SIMATIC WinCC Vulnerabilities

  • Siemens Multiple SIMATIC HMI panels (TP, OP, MP, Comfort Panels, Mobile Panels) Siemens WinCC flexible 2004, 2005, 2007, 2008 Siemens WinCC flexible Runtime Siemens WinCC V11 (TIA portal) Siemens WinCC V11 Runtime Advanced
    affected: mitigation “WinCC V11 (TIA Portal) SP2 Update 1, (http://support.automation.siemens.com/WW/view/en/58112587)”

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.61% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.