Simatic S7 Cpu 1200 FirmwareOperating system · Siemens

CVE-2014-2254

HIGH · 7.8 CVSS v2.0 Published 2014-03-24
Fix available
A fix is available. Upgrade to after 3.0.2 or later.
See remediation →
87/100
Remediation priority · High
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
Siemens SIMATIC S7-1200 CPU PLC devices with firmware before 4.0 allow remote attackers to cause a denial of service (defect-mode transition) via crafted HTTP packets, a different vulnerability than CVE-2014-2255.

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 · high confidence

Siemens SIMATIC S7-1200 CPU PLC devices with firmware versions prior to 4.0 contain a denial-of-service vulnerability where remote attackers can send crafted HTTP packets to trigger a defect-mode transition, causing the PLC to enter a fault state and cease normal operations.

MitigationUpdate SIMATIC S7-1200 firmware to version 4.0 or later to remediate this vulnerability. Additionally, restrict network access to the PLC's HTTP interface using firewalls or network segmentation to limit exposure to unauthenticated HTTP-based attacks.

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
Simatic S7 Cpu 1200 FirmwareOperating system
Affected:<= 3.0.2= 3.0
Simatic S7 Cpu 1211cHardware / appliance
Affected:all versions
Simatic S7 Cpu 1212cHardware / appliance
Affected:all versions
Simatic S7 Cpu 1214cHardware / appliance
Affected:all versions
Simatic S7 Cpu 1215cHardware / appliance
Affected:all versions
Simatic S7 Cpu 1217cHardware / appliance
Affected:all versions

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

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

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 the SIMATIC S7-1200 CPU model
    Access the PLC via TIA Portal, STEP 7, or the PLC's built-in web server to read the device nameplate or device identification. Look for model numbers such as 1211c, 1212c, 1214c, 1215c, 1217c, or generic S7-1200 CPU.
    Affected if The CPU model is any of the following: 1211c, 1212c, 1214c, 1215c, or 1217c (all versions of these models are affected).
  2. Check the firmware version of the S7-1200 CPU
    Retrieve the firmware version through the TIA Portal device overview, the PLC's web interface under 'Device Information', or via STEP 7/STEP 7 MicroWin by accessing the CPU properties. Note the exact firmware version number.
    Affected if The firmware version is 3.0, 3.0.2, or any version lower than 3.0.2 (firmware <= 3.0.2). Note that models 1211c, 1212c, 1214c, 1215c, and 1217c are affected at ALL versions regardless of firmware.
  3. Determine if the HTTP web interface is enabled
    Access the PLC configuration in TIA Portal or STEP 7 and check the 'Web Server' settings under the CPU properties. Alternatively, attempt to access the PLC's IP address via HTTP from a browser to see if a web page loads.
    Affected if The HTTP web server is enabled and accessible on the network, as this is the attack vector for the crafted HTTP packets.
  4. Verify the PLC operational status
    Check the PLC status via TIA Portal online diagnostics, STEP 7, or by observing the LED indicators on the physical PLC module (specifically the RUN/STOP and ERROR lights).
    Affected if The PLC is in DEFECT mode, FAULT state, or showing ERROR status indicators, which may indicate successful exploitation of this vulnerability.

Your environment is affected if you have a SIMATIC S7-1200 CPU model 1211c, 1212c, 1214c, 1215c, or 1217c at any version, or any S7-1200 CPU with firmware version 3.0.2 or lower, and the HTTP web interface is enabled and exposed on the network.

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
Upgrade available Upgrade to a release after 3.0.2
Interim mitigation

Update SIMATIC S7-1200 firmware to version 4.0 or later to remediate this vulnerability. Additionally, restrict network access to the PLC's HTTP interface using firewalls or network segmentation to limit exposure to unauthenticated HTTP-based attacks.

Fix this in Simatic S7 Cpu 1200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2014-2254 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