dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2023-36754

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 SCEP server configuration 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

A command injection vulnerability exists in the SCEP server configuration URL parameter of the RUGGEDCOM ROX web interface. Due to missing server-side input sanitization, an authenticated privileged attacker can inject arbitrary shell commands through the URL parameter, which execute with root privileges on the underlying Linux system.

MitigationUpgrade all affected RUGGEDCOM ROX devices (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) to firmware version V2.16.0 or later to remediate this vulnerability.

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 device model and firmware version
    Access the RUGGEDCOM ROX web interface and navigate to the System > Firmware or About page to view the installed firmware version. Alternatively, use the CLI command 'show version' or equivalent to retrieve the firmware version.
    Affected if The firmware version is below 2.16.0 (e.g., V2.15.x, V2.14.x, etc.)
  2. Confirm device model is in affected product list
    Check the device model identification in the web interface System Information or on the physical device label. The affected models are: MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512.
    Affected if The device is one of the listed models with firmware < 2.16.0
  3. Verify SCEP server feature is enabled
    Navigate to the SCEP server configuration section in the RUGGEDCOM ROX web interface (typically under PKI or Certificate settings). Check if the SCEP server is configured and enabled.
    Affected if The SCEP server feature is enabled and a URL parameter is configurable for the SCEP server endpoint
  4. Check web interface accessibility
    Attempt to access the RUGGEDCOM ROX web interface over HTTPS/HTTP. The vulnerability requires an authenticated privileged attacker, so verify whether remote web management is accessible.
    Affected if The web interface is accessible from a network where untrusted authenticated users could connect

You are affected if your RUGGEDCOM ROX device (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, or RX1512) runs firmware version below 2.16.0, has the SCEP server feature enabled, and the web interface is accessible to authenticated users.

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 all affected RUGGEDCOM ROX devices (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) to firmware version V2.16.0 or later to remediate this vulnerability.

Recommended fix High confidence

V2.16.0

  1. 1. Identify the specific Ruggedcom ROX device model from the affected list (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512).
  2. 2. Obtain the fixed firmware version V2.16.0 or later from the Siemens industrial security portal or official support channels (cert-portal.siemens.com).
  3. 3. Review the device's firmware upgrade documentation for the specific model to understand the upgrade procedure.
  4. 4. Back up the current device configuration according to Siemens backup procedures.
  5. 5. Upload the V2.16.0 firmware to the device through the web interface or management interface as documented.
  6. 6. After upgrade, verify the SCEP server configuration parameter now properly sanitizes input.
  7. 7. Confirm the device is running firmware version V2.16.0 or later.

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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