CVE-2017-6864
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 · uneditedThe integrated web server in Siemens RUGGEDCOM ROX I (all versions) at port 10000/TCP could allow an authenticated user to perform stored Cross-Site Scripting attacks.
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 confidenceA stored Cross-Site Scripting vulnerability exists in the integrated web server of Siemens RUGGEDCOM ROX I devices on port 10000/TCP. An authenticated user can inject malicious JavaScript code that gets persisted on the device and executes when other users access the affected web content.
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<= 2.9.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
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 Siemens RUGGEDCOM ROX I device on networkCheck network inventory or scan for device fingerprints (manufacturer: Siemens, product: RUGGEDCOM ROX) on port 10000/TCP using nmap: nmap -p 10000 -sV <target>Affected if Device is confirmed as Siemens RUGGEDCOM ROX I with web server on port 10000/TCP
-
Confirm web server is accessible on port 10000/TCPVerify TCP port 10000 is open and responding: nmap -p 10000 <target> or telnet <target> 10000Affected if Port 10000/TCP is open and serves HTTP content
-
Check if web authentication is requiredAccess the web interface via browser or curl on port 10000 and observe whether a login prompt appears. For authenticated checks, log in with valid credentials.Affected if Web interface allows authenticated access (login page present or credentials accepted)
-
Determine installed ROX firmware versionAccess the web UI and navigate to System Information or Administration > Firmware Version page; alternatively, check via CLI: show version or login to device management interfaceAffected if Firmware version is 2.9.0 or lower
-
Verify stored XSS payload presenceAs an authenticated user, navigate to web forms where user input is stored (such as device name, description fields, or user profile settings). Check source HTML of pages for unsanitized user-provided values using browser DevTools or curl to inspect rendered output.Affected if User-supplied input appears in HTML output without proper encoding (e.g., <script> tags visible in page source)
A user is affected if they have a Siemens RUGGEDCOM ROX I device with firmware version 2.9.0 or lower, with the web server on port 10000/TCP accessible to authenticated users, and where stored user input renders without encoding.
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 dataApply vendor-supplied firmware updates when available; implement input validation and output encoding on web application inputs as a compensating control; restrict web server access to authorized personnel only.
- 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-6864 — 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-6864 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