CVE-2013-2780
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 UDP port 161 (aka the SNMP 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 · moderate confidenceSiemens SIMATIC S7-1200 PLCs versions 2.x and 3.x contain a denial-of-service vulnerability where remote attackers can send crafted packets to UDP port 161 (SNMP), causing the device to enter defect-mode and resulting in a control outage.
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 modelLocate the CPU type label on the physical device or check the device configuration in the TIA Portal engineering software. Common affected models include 1211c, 1212c, 1212fc, 1214c, 1214fc, 1215c, and 1215fc.Affected if The CPU model is any of the Simatic S7-1200 variants (1211c, 1212c, 1212fc, 1214c, 1214fc, 1215c, 1215fc).
-
Check the installed firmware versionAccess the PLC via the TIA Portal or web interface, or use the device's online diagnostics to retrieve the current firmware version. Compare it to the affected range.Affected if The firmware version is 2.x or 3.x, which are versions less than 4.0.
-
Verify if SNMP is enabled on the deviceCheck the PLC configuration settings in TIA Portal or the device web interface for SNMP service status. SNMP is typically configured under the device properties or communication settings.Affected if SNMP is enabled and configured on the PLC.
-
Confirm UDP port 161 exposureScan the network to determine if UDP port 161 on the PLC is accessible from untrusted networks. Use network scanning tools or review firewall rules and access control lists.Affected if UDP port 161 is reachable from external or untrusted network segments.
The environment is affected if the device is an S7-1200 PLC with firmware version below 4.0, SNMP is enabled, and UDP port 161 is network-accessible.
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 or block external access to UDP port 161 on PLCs, implement network segmentation to isolate PLCs from untrusted networks, and apply vendor-supplied firmware updates when available.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2780 — 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-2780 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