CVE-2017-12736
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 · uneditedAfter initial configuration, the Ruggedcom Discovery Protocol (RCDP) is still able to write to the device under certain conditions. This could allow an attacker located in the adjacent network of the targeted device to perform unauthorized administrative actions.
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 confidenceThe Ruggedcom Discovery Protocol (RCDP) on Siemens Ruggedcom devices remains writable after initial device configuration under certain conditions. This allows an attacker with adjacency to the targeted network to send write commands via RCDP and perform unauthorized administrative actions on the device.
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.0>= 3.0>= 3.0>= 3.0>= 6.1>= 6.1< 5.0.1< 4.3.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 device modelLog into the device web interface or CLI and locate the device name/model information (typically found in System > Device Information or similar location). Confirm it is one of the affected product lines: Scalance Xb 200, Xc 200, Xp 200, Xr300 Wg, Xr 500, Xm 400, or Ruggedcom ROS devices.Affected if Device model is one of the listed affected products.
-
Check firmware versionIn the device web interface or CLI, locate the firmware version information (often under System > Software or Device Information). Compare your installed firmware version against the affected ranges: >= 3.0 for Scalance Xb/Xc/Xp 200 and Xr300 Wg; >= 6.1 for Scalance Xr 500 and Xm 400; < 5.0.1 or < 4.3.4 for Ruggedcom ROS.Affected if Firmware version falls within the affected ranges listed.
-
Verify RCDP configuration statusAccess the device configuration settings and locate the Ruggedcom Discovery Protocol (RCDP) settings (typically under Network Services, Discovery Protocol, or similar menu). Check whether RCDP is still enabled and whether it remains in writable mode after initial setup.Affected if RCDP is enabled and remains writable after initial device configuration.
-
Confirm RCDP service accessibilityFrom a network segment adjacent to the device, attempt to reach the RCDP service port (port 9999 for Ruggedcom devices). Use network scanning tools or check firewall rules to determine if the RCDP service is accessible from network segments beyond the initial configuration segment.Affected if RCDP service is accessible from network segments outside the trusted management network.
Your device is affected if it is a Siemens Scalance or Ruggedcom device with a firmware version in the affected ranges AND RCDP remains enabled and writable after initial configuration AND the RCDP service is accessible from your 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 data4.3.45.0.1
Disable RCDP after initial device configuration or restrict network access to prevent adjacent network attackers from reaching the RCDP service. Implement network segmentation to isolate industrial control devices.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12736 — 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-12736 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