CVE-2013-0700
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-1200 PLCs 2.x and 3.x allow remote attackers to cause a denial of service (defect-mode transition and control outage) via crafted packets to TCP port 102 (aka the ISO-TSAP port).
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-1200 PLCs versions 2.x and 3.x contain a vulnerability where remote attackers can send crafted packets to TCP port 102 (ISO-TSAP), the protocol used for S7 communication. This causes the PLC to transition to defect mode, resulting in a denial of service and loss of control operations.
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< 4.0< 4.0< 4.0< 4.0< 4.0< 4.0< 4.0< 4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the S7-1200 CPU modelCheck the device labeling on the PLC physical housing, or access the device via TIA Portal project properties, or view the device overview in the web-based management interface. Look for model numbers such as 1211c, 1212c, 1212fc, 1214Fc, 1214c, 1215Fc, or 1215c.Affected if The device is a Siemens Simatic S7-1200 CPU of the models listed in the affected products
-
Check the PLC firmware versionAccess the PLC through TIA Portal and view the device properties to read the firmware version, or use the web-based management portal of the PLC, or check the version displayed on the PLC's physical display under device information. Record the firmware version number.Affected if The firmware version is 2.x or 3.x, meaning any version less than 4.0
-
Verify TCP port 102 accessibilityUse a network scanning tool such as nmap or PowerShell Test-NetConnection to probe TCP port 102 (ISO-TSAP) on the PLC IP address. This is the default port for S7 communication.Affected if TCP port 102 is reachable from network segments that are not trusted or are exposed to external systems
-
Check PLC operational statusAccess the PLC diagnostics in TIA Portal, check the web-based management status page, or observe the physical LED indicators on the PLC. Specifically look for indicators of defect mode or communication failures.Affected if The PLC is in defect mode, showing STOP with a red SF or BF LED, or experiencing communication failures on port 102
A user is affected if they have a Siemens Simatic S7-1200 CPU (1211c, 1212c, 1212fc, 1214Fc, 1214c, 1215Fc, or 1215c) running firmware version less than 4.0, with TCP port 102 accessible from an untrusted network segment.
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 data4.0
Restrict network access to TCP port 102 on affected PLCs using network segmentation and firewalls; apply Siemens firmware updates to resolve the vulnerability.
- Consultation8.0 h
- Implementation12.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0700 — 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-2013-0700 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