dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2023-36751

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 install-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

Command injection vulnerability in the install-app URL parameter of the RUGGEDCOM ROX web interface due to missing server-side input sanitization. An authenticated privileged attacker can execute arbitrary code with root privileges on affected devices (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) running versions prior to V2.16.0.

MitigationUpgrade RUGGEDCOM ROX devices to version V2.16.0 or later to remediate this vulnerability. Limit web interface access to trusted networks and privileged users until the patch is applied.

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 device model
    Check the RUGGEDCOM device label or access the web interface to view the device information. The affected models are: MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000.
    Affected if The device model matches one of the listed affected models.
  2. Determine the firmware version
    Log into the RUGGEDCOM ROX web interface and navigate to the System Info or About section to view the firmware version. Alternatively, use the CLI and run 'show version' or check the firmware file name if accessible.
    Affected if The installed firmware version is earlier than V2.16.0.
  3. Confirm the web interface is enabled
    Check if the RUGGEDCOM ROX web interface (HTTP/HTTPS) is listening and accessible on the device. This can be done by attempting to reach the device IP via a browser or running a port scan against ports 80/443.
    Affected if The web interface is exposed and accessible.
  4. Verify the install-app functionality exists
    Access the web interface and check if there is an 'install-app' URL endpoint or an application installation feature available in the administrative interface.
    Affected if The install-app functionality is present and accessible to authenticated users.

The device is affected if it is a listed RUGGEDCOM ROX model running firmware version earlier than V2.16.0 and has the web interface with install-app functionality enabled.

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 RUGGEDCOM ROX devices to version V2.16.0 or later to remediate this vulnerability. Limit web interface access to trusted networks and privileged users until the patch is applied.

Recommended fix High confidence

V2.16.0

  1. Identify the current Ruggedcom ROX device model and firmware version via the web interface or CLI
  2. Access the Siemens CERT portal or Siemens Industrial Security website to download firmware version V2.16.0 for your specific device model
  3. Review the firmware upgrade instructions in the Siemens product documentation before proceeding
  4. Back up the current device configuration to enable restoration if needed
  5. Ensure stable power supply to the device during the firmware upgrade process
  6. Upload and apply firmware V2.16.0 using the device's firmware upgrade function via the web interface or CLI
  7. After reboot, verify the firmware version shows V2.16.0 in the web interface or CLI
  8. Confirm the install-app functionality works correctly and the vulnerability is remediated

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

Fix this in Ruggedcom Rox Mx5000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
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,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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