dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2023-36752

HIGH · 7.2 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 2.16.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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). The upgrade-app URL parameter in the web interface of affected devices is vulnerable to command injection due to missing server side input sanitation. This could allow an authenticated privileged remote attacker to execute arbitrary code with root privileges.

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

The upgrade-app URL parameter in the web interface of RUGGEDCOM ROX devices lacks server-side input sanitization, allowing an authenticated privileged attacker to inject OS commands that execute with root privileges. This is a direct command injection vulnerability in the firmware upgrade functionality.

MitigationUpgrade affected devices to firmware version V2.16.0 or later. Restrict web interface access to trusted networks and ensure privileged accounts use strong, unique credentials to reduce attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 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 the CLI command 'show version' to determine the exact model (Mx5000, Mx5000re, Rx1400, Rx1500, Rx1501, Rx1510, Rx1511, or Rx1512)
    Affected if The device model is any of the eight affected models listed in the CVE
  2. Determine the installed firmware version
    In the web interface, navigate to System > Device Information or use the CLI command 'show version' to read the firmware version installed on the device
    Affected if The firmware version is below 2.16.0
  3. Confirm web interface is enabled
    Check if the web interface (HTTP/HTTPS) is listening by accessing the device IP in a browser or using a port scanner against ports 80 and 443
    Affected if The web interface is accessible on the network
  4. Verify the upgrade-app functionality exists
    Attempt to access the firmware upgrade page in the web interface, typically found under Administration > Firmware Upgrade or System > Upgrade
    Affected if The firmware upgrade functionality is present and accessible to authenticated users

A user is affected if they have a RUGGEDCOM ROX device (any of the eight listed models) running firmware below version 2.16.0 with the web interface accessible on the network.

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 devices to firmware version V2.16.0 or later. Restrict web interface access to trusted networks and ensure privileged accounts use strong, unique credentials to reduce attack surface.

Recommended fix High confidence

V2.16.0 or later

  1. 1. Identify the current firmware version of the Ruggedcom ROX device by accessing the web interface or checking via CLI.
  2. 2. Navigate to the Siemens industrial security portal at cert-portal.siemens.com to download the fixed firmware version V2.16.0 or later for your specific device model.
  3. 3. Review the Siemens upgrade instructions for Ruggedcom ROX devices before proceeding with the update.
  4. 4. Apply the firmware upgrade to the affected device through the web interface or management console, following the documented upgrade procedure.
  5. 5. After upgrading, verify that the firmware version is now V2.16.0 or later.
  6. 6. Confirm that the upgrade-app functionality is now properly sanitized and the command injection vulnerability is resolved.
Caveat Review Siemens release notes for any configuration or compatibility changes between your current version and V2.16.0 before upgrading

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36752 — 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-36752 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