dbcve.org
Ruggedcom Rox Ii FirmwareOperating system · Siemens

CVE-2024-56839

HIGH · 7.2 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 2.17.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.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). Code injection can be achieved when the affected device is using VRF (Virtual Routing and Forwarding). An attacker could leverage this scenario to execute arbitrary code as root user.

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 code injection vulnerability in RUGGEDCOM ROX devices (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) allows remote attackers to execute arbitrary code as root when VRF (Virtual Routing and Forwarding) is enabled. The vulnerability exists in all versions prior to V2.17.0.

MitigationUpgrade affected devices to firmware version V2.17.0 or later. If patching is not immediately feasible, disable VRF if not required or implement strict network access controls 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 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
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
    Access the device CLI or web interface and run 'show system-info' or check the device nameplate. Confirm the model is one of: MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000
    Affected if Device model is NOT in this list (the vulnerability only affects these specific Ruggedcom ROX models)
  2. Check firmware version
    Run 'show version' or 'show system-info' in the device CLI. Look for the firmware version number displayed in the output
    Affected if Firmware version is 2.17.0 or later (the vulnerability affects versions PRIOR to V2.17.0)
  3. Verify VRF is enabled
    Run 'show vrf' or 'show ip vrf' in the device CLI to display VRF instances and their status. Check if any VRF instances are configured and active
    Affected if VRF is NOT enabled (the code injection vulnerability only triggers when VRF is enabled; if VRF is disabled, the attack surface does not exist)
  4. Check VRF configuration details
    Run 'show running-config | include vrf' or access the VRF configuration section via 'configure' mode to list all VRF configurations
    Affected if No VRF instances exist in the configuration (this confirms the vulnerability cannot be exploited even on older firmware)

Device is affected only if it is a listed Ruggedcom ROX model, runs firmware version prior to 2.17.0, AND has VRF enabled in the configuration.

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 affected devices to firmware version V2.17.0 or later. If patching is not immediately feasible, disable VRF if not required or implement strict network access controls to reduce attack surface.

Recommended fix High confidence

V2.17.0 or later

  1. Identify the specific Ruggedcom ROX model (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000) that requires remediation
  2. Obtain the firmware version V2.17.0 or later from the official Siemens/Cert-portal support channels
  3. Review Siemens upgrade documentation and release notes for the target device before proceeding
  4. Schedule a maintenance window since firmware upgrades typically require device downtime
  5. Perform a complete backup of the current device configuration
  6. Follow the official firmware upgrade procedure specific to the device model (usually via web UI, CLI, or USB upgrade)
  7. After upgrade, verify the firmware version shows V2.17.0 or later
  8. Confirm VRF functionality operates normally and the vulnerability is remediated
Caveat Firmware upgrades on industrial devices may introduce compatibility changes with existing configurations or connected systems; review release notes before upgrading

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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