CVE-2017-2681
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 packets sent on a local Ethernet segment (Layer 2) to an affected product could cause a denial of service condition of that product. Human interaction is required to recover the system. 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 · high confidenceVulnerability in PROFINET DCP (Discovery and Configuration Protocol) allows specially crafted packets at Layer 2 to cause a denial of service condition on affected devices. The attack requires the attacker to be on the same local Ethernet segment (adjacent network), and recovery requires human intervention.
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 the communication processor modelLocate the Siemens SIMATIC CP module on the PLC rack or in the hardware catalog. Common models include Cp 343-1, Cp 443-1, Cp 1243-1, or Cm 1542-1 variants (Std/Lean/Adv/OPC UA).Affected if The model matches one of the affected products: Cp 343-1 (any variant), Cp 443-1 (any variant), Cp 1243-1, or Cm 1542-1.
-
Check the installed firmware versionAccess the device via TIA Portal, Web interface, or console and retrieve the firmware version. Compare against the affected ranges: Cp 343-1 Std/Lean < 3.1.3, Cp 343-1 Adv all versions, Cp 443-1 Std/Adv < 3.2.17, Cp 443-1 OPC UA all versions, Cp 1243-1 < 2.1.82, Cm 1542-1 < 2.0.Affected if The installed firmware version is lower than the specified threshold for that model, or the model is listed as affected in all versions.
-
Determine network accessibilityVerify whether the affected device is on a shared Ethernet segment with untrusted systems. Check if the device is isolated on a dedicated VLAN or has proper Layer 2 access controls.Affected if The device is reachable by an adjacent attacker on the same local Ethernet segment without network segmentation or filtering.
-
Confirm PROFINET DCP is activePROFINET DCP is enabled by default on PROFINET-capable CP modules. Verify PROFINET configuration in TIA Portal or check if the device responds to DCP Identify requests on the network.Affected if PROFINET DCP protocol is enabled and operational on the device (default state for affected models).
You are affected if you have any of the listed CP models with a vulnerable firmware version and the device is accessible on a shared Layer 2 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 data2.02.1.823.1.3
Isolate affected PROFINET devices on separate network segments or VLANs to limit Layer 2 access; implement packet filtering at network boundaries to block unauthorized PROFINET DCP packets; consult vendor for available patches.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2681 — 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-2681 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