dbcve.org
Ruggedcom Rox Ii FirmwareOperating system · Siemens

CVE-2024-56835

HIGH · 8.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 2.17.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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.17.0), RUGGEDCOM ROX MX5000RE (All versions < V2.17.0), RUGGEDCOM ROX RX1400 (All versions < V2.17.0), RUGGEDCOM ROX RX1500 (All versions < V2.17.0), RUGGEDCOM ROX RX1501 (All versions < V2.17.0), RUGGEDCOM ROX RX1510 (All versions < V2.17.0), RUGGEDCOM ROX RX1511 (All versions < V2.17.0), RUGGEDCOM ROX RX1512 (All versions < V2.17.0), RUGGEDCOM ROX RX1524 (All versions < V2.17.0), RUGGEDCOM ROX RX1536 (All versions < V2.17.0), RUGGEDCOM ROX RX5000 (All versions < V2.17.0). The DHCP Server configuration file of the affected products is subject to code injection. An attacker could leverage this vulnerability to spawn a reverse shell and gain root access on the affected system.

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

Code injection vulnerability in the DHCP Server configuration file of RUGGEDCOM ROX devices (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) allows attackers to inject malicious code that gets executed, enabling reverse shell spawning and root access to the affected system.

MitigationUpgrade all affected RUGGEDCOM ROX devices to firmware version V2.17.0 or later. Until patched, restrict network access to the DHCP server configuration interface using firewall rules or network segmentation to prevent unauthorized access.

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 Ii FirmwareOperating system
Affected:< 2.17.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Confirm device model is affected
    Access the device's web interface or CLI and identify the exact model number. Verify it matches one of: MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000.
    Affected if Device model is one of the listed RUGGEDCOM ROX models
  2. Check firmware version
    Access the device's web interface (typically via System > Software or About section) or CLI and retrieve the installed firmware version. Compare against the affected range of versions earlier than 2.17.0.
    Affected if Firmware version is below V2.17.0
  3. Verify DHCP Server is enabled
    Access the device's web interface or CLI and navigate to the DHCP Server configuration section. Check whether the DHCP Server service is currently enabled or configured.
    Affected if DHCP Server is enabled or has been configured on the device
  4. Inspect DHCP Server configuration for unauthorized changes
    Access the DHCP Server configuration file or settings panel. Review all DHCP options, custom scripts, or command fields for unexpected or suspicious content such as shell commands, network connections, or base64-encoded payloads.
    Affected if DHCP Server configuration contains unexpected commands, scripts, or suspicious strings that were not intentionally added by the administrator

A device is affected if it is a RUGGEDCOM ROX model from the list, runs firmware earlier than V2.17.0, and has the DHCP Server feature enabled or configured.

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.17.0 or later
Fixed in 2.17.0
Interim mitigation

Upgrade all affected RUGGEDCOM ROX devices to firmware version V2.17.0 or later. Until patched, restrict network access to the DHCP server configuration interface using firewall rules or network segmentation to prevent unauthorized access.

Recommended fix High confidence

V2.17.0

  1. Obtain the V2.17.0 firmware from Siemens' official support portal (cert-portal.siemens.com or siemens.com/support) for your specific RUGGEDCOM ROX model
  2. Verify the integrity of the downloaded firmware image using checksums if provided by Siemens
  3. Back up the current device configuration before initiating the upgrade
  4. Access the RUGGEDCOM ROX web interface or CLI and navigate to the firmware upgrade section
  5. Upload the V2.17.0 firmware image and initiate the upgrade process
  6. Allow the device to complete the upgrade and reboot automatically
  7. After the device restarts, verify the firmware version displays as V2.17.0 in the system information
  8. Verify that the DHCP Server service is functioning correctly and accepting configuration without injection vulnerabilities

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

Fix this in Ruggedcom Rox Ii Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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