CVE-2016-2200
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 · uneditedSiemens SIMATIC S7-1500 CPU devices before 1.8.3 allow remote attackers to cause a denial of service (STOP mode transition) via crafted packets on TCP port 102.
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 confidenceSiemens SIMATIC S7-1500 CPU devices before firmware version 1.8.3 contain a vulnerability where remote attackers can send specially crafted packets to TCP port 102 (S7comm protocol), causing the PLC to transition to STOP mode and resulting in a denial of service condition.
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<= 1.8.2CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is SIMATIC S7-1500 CPUAccess the PLC via TIA Portal, web interface, or physical HMI and verify the device type is specifically a SIMATIC S7-1500 CPU. Other S7 series (S7-300, S7-1200, S7-400) are not affected by this CVE.Affected if Device is any SIMATIC S7-1500 CPU model
-
Check installed firmware versionVia TIA Portal: go to Online Access > select device > Online & Diagnostics > Diagnostics > General. Or via web server: access device IP and check firmware version under Device Information. Compare against affected range: <= 1.8.2.Affected if Firmware version is 1.8.2 or lower
-
Verify TCP port 102 exposurePerform a network port scan of the PLC IP address targeting TCP port 102 (S7comm). Use command: nmap -p 102 -sV <PLC_IP_ADDRESS>. Confirm port is open and reachable from network segments.Affected if TCP port 102 is open and accessible from network (not isolated orfirewalled)
-
Check PLC operational stateVia TIA Portal Online & Diagnostics, or via the PLC's web interface, or by observing physical HMI status indicators. Look for current mode: RUN, STOP, or STARTUP.Affected if Device has been forced into STOP mode unexpectedly, indicating possible exploitation
Device is affected if it is a SIMATIC S7-1500 CPU running firmware version 1.8.2 or lower AND TCP port 102 is accessible on the network.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade SIMATIC S7-1500 CPU devices to firmware version 1.8.3 or later. If immediate patching is not feasible, implement network segmentation to restrict unauthorized access to TCP port 102 and consider compensating controls such as firewalls or IPS to detect/block malicious S7comm traffic.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2200 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-2200 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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