CVE-2017-2680
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 · uneditedSpecially crafted PROFINET DCP broadcast packets could cause a denial of service condition of affected products on a local Ethernet segment (Layer 2). Human interaction is required to recover the systems. PROFIBUS interfaces are not affected.
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 confidenceA specially crafted PROFINET DCP broadcast packet can cause a denial of service on affected industrial control products operating on a local Ethernet segment (Layer 2). The vulnerability allows an attacker on the same network segment to crash affected devices, which then require manual human intervention to restore normal operation.
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< 3.1.3< 3.1.3all versions< 3.2.17< 3.2.17all versions< 2.1.82< 2.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify installed Siemens CP/CM modulesLocate all Simatic CP 343-1, CP 443-1, CP 1243-1, and CM 1542-1 modules in the industrial network inventory or physically inspect the hardware for model labelsAffected if Any of these modules (Cp 343 1 Std, Cp 343 1 Lean, Cp 343 1 Adv, Cp 443 1 Std, Cp 443 1 Adv, Cp 443 1 Opc Ua, Cp 1243 1, Cm 1542 1) are present
-
Check firmware version on CP 343-1 Std or LeanAccess the module via TIA Portal, STEP 7, or web interface and retrieve the firmware version from the module properties or diagnosticsAffected if Firmware version is below 3.1.3
-
Check firmware version on CP 343-1 AdvAccess the module via TIA Portal, STEP 7, or web interface and retrieve the firmware version from the module properties or diagnosticsAffected if Any firmware version (all versions affected)
-
Check firmware version on CP 443-1 Std or AdvAccess the module via TIA Portal, STEP 7, or web interface and retrieve the firmware version from the module properties or diagnosticsAffected if Firmware version is below 3.2.17
-
Check firmware version on CP 443-1 Opc UaAccess the module via TIA Portal, STEP 7, or web interface and retrieve the firmware version from the module properties or diagnosticsAffected if Any firmware version (all versions affected)
-
Check firmware version on CP 1243-1 and CM 1542-1Access the module via TIA Portal, STEP 7, or web interface and retrieve the firmware version from the module properties or diagnosticsAffected if CP 1243-1 firmware is below 2.1.82, or CM 1542-1 firmware is below 2.0
The environment is affected if any of the listed Simatic CP/CM modules are present AND their firmware version falls within the vulnerable ranges specified (or is an 'all versions' affected variant), AND the device is accessible on a local Ethernet segment where a malicious PROFINET DCP broadcast packet could be injected.
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 data2.02.1.823.1.3
Apply vendor-specific patches when available; otherwise implement network segmentation or VLAN isolation to limit broadcast domain exposure and restrict unauthorized Layer 2 access to the industrial network segment.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2680 — 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-2017-2680 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