CVE-2017-2689
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 RUGGEDCOM ROX I (all versions) allow an authenticated user to bypass access restrictions in the web interface at port 10000/TCP to obtain privileged file system access or change configuration settings.
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 confidenceSiemens RUGGEDCOM ROX I contains an access control bypass vulnerability in its web interface on port 10000/TCP. An authenticated user with standard privileges can circumvent access restrictions to gain privileged file system access or modify configuration settings that should be restricted to higher-privilege users.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 installed RUGGEDCOM ROX I versionAccess the device console or web interface and locate the firmware version information, typically found in system status or about settings. Compare the displayed version number against the affected range.Affected if The displayed firmware version is 2.9.0 or lower.
-
Verify web interface availability on port 10000/TCPRun a network port scan or use a command such as 'nc -zv <device_ip> 10000' or 'telnet <device_ip> 10000' to confirm the web interface port is listening and accessible.Affected if Port 10000/TCP is open and reachable from the network being assessed.
-
Confirm presence of standard privilege usersLog into the RUGGEDCOM ROX web interface and review user accounts. Check if any users are assigned roles with standard or limited privileges rather than administrator-level access.Affected if One or more standard privilege user accounts exist on the system.
-
Check for accessible privileged functionsUsing a standard privilege account, attempt to access restricted areas such as file system browsing, configuration modification for sensitive settings, or administrative menus that should require elevated privileges.Affected if A standard privilege user can access files, modify settings, or perform actions that should be restricted to administrative roles.
The environment is affected if RUGGEDCOM ROX I version 2.9.0 or lower is installed, the web interface on port 10000/TCP is network-accessible, and standard privilege users exist who can circumvent access controls to reach privileged functionality.
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 the vendor-supplied firmware patch when available. Until then, restrict network access to port 10000/TCP to only trusted management networks and monitor for unauthorized configuration changes.
- Consultation4.0 h
- Implementation3.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2689 — 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-2689 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