dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2023-36390

MEDIUM · 5.4 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 2.16.0 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0), RUGGEDCOM ROX RX1400 (All versions < V2.16.0), RUGGEDCOM ROX RX1500 (All versions < V2.16.0), RUGGEDCOM ROX RX1501 (All versions < V2.16.0), RUGGEDCOM ROX RX1510 (All versions < V2.16.0), RUGGEDCOM ROX RX1511 (All versions < V2.16.0), RUGGEDCOM ROX RX1512 (All versions < V2.16.0), RUGGEDCOM ROX RX1524 (All versions < V2.16.0), RUGGEDCOM ROX RX1536 (All versions < V2.16.0), RUGGEDCOM ROX RX5000 (All versions < V2.16.0). A reflected cross-site scripting (XSS) vulnerability exists in the web interface of the affected application that could allow an attacker to execute malicious javascript code by tricking users into accessing a malicious link. The value is reflected in the response without sanitization while throwing an “invalid params element name” error on the action parameters.

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 confidence

A reflected cross-site scripting (XSS) vulnerability exists in the web interface of multiple RUGGEDCOM ROX network devices. The vulnerability occurs when user-supplied input in action parameters is reflected in the error response ('invalid params element name' error) without proper sanitization, allowing attackers to execute malicious JavaScript code by tricking users into clicking crafted malicious links.

MitigationUpgrade affected RUGGEDCOM ROX devices to firmware version V2.16.0 or later. Until upgrade is possible, implement URL filtering and user training to prevent users from accessing malicious links.

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
Ruggedcom Rox Mx5000 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Mx5000re FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1400 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1500 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1501 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1510 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1511 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1512 FirmwareOperating system
Affected:< 2.16.0

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the RUGGEDCOM ROX device model
    Access the device web interface or use SNMP to determine the exact model number (Mx5000, Mx5000re, Rx1400, Rx1500, Rx1501, Rx1510, Rx1511, or Rx1512)
    Affected if The device model is any of the listed affected models
  2. Check the installed firmware version
    Log into the device web interface and navigate to the System Information or Firmware version page, or use the CLI command 'show version' to retrieve the firmware version
    Affected if The firmware version is below 2.16.0
  3. Verify web interface is enabled
    Check the device configuration to confirm the web interface (HTTP/HTTPS) service is enabled and accessible from the network
    Affected if The web interface is enabled and reachable on the network
  4. Confirm web login access
    Attempt to access the device login page via HTTP or HTTPS to verify the web interface is responding
    Affected if The web interface responds to HTTP/HTTPS requests

A user is affected if they have a RUGGEDCOM ROX device (Mx5000, Mx5000re, Rx1400, Rx1500, Rx1501, Rx1510, Rx1511, or Rx1512) running firmware version below 2.16.0 with the web interface enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.16.0 or later
Fixed in 2.16.0
Interim mitigation

Upgrade affected RUGGEDCOM ROX devices to firmware version V2.16.0 or later. Until upgrade is possible, implement URL filtering and user training to prevent users from accessing malicious links.

Recommended fix High confidence

Ruggedcom ROX firmware V2.16.0

  1. 1. Obtain the Ruggedcom ROX firmware version 2.16.0 or later from Siemens' official support portal or cert-portal.siemens.com
  2. 2. Back up the current device configuration to ensure data preservation before upgrading
  3. 3. Access the Ruggedcom ROX device web interface or management console
  4. 4. Navigate to the firmware update or system upgrade section
  5. 5. Upload and install the firmware version 2.16.0 or later
  6. 6. Verify the upgrade was successful by checking the firmware version in the system information
  7. 7. Confirm the web interface is functioning properly after the upgrade
  8. 8. Test that the previously vulnerable endpoint no longer reflects unsanitized input
Caveat Review Siemens release notes for any configuration or feature changes between your current version and V2.16.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ruggedcom Rox Mx5000 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36390 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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