Ruggedcom Rox Ii FirmwareOperating system · Siemens

CVE-2024-56840

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

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). Under certain conditions, IPsec may allow code injection in the affected device. An attacker could leverage this scenario to execute arbitrary code as root user.

Technical summary

dbcve analysis · high confidence

A code injection vulnerability exists in the IPsec implementation of multiple RUGGEDCOM ROX devices (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) running firmware versions prior to V2.17.0. The vulnerability allows an attacker to inject and execute arbitrary code with root privileges on the affected device.

MitigationUpgrade RUGGEDCOM ROX firmware to version V2.17.0 or later to remediate the IPsec code injection vulnerability. Prior to upgrading, coordinate a maintenance window and backup configurations as these are critical infrastructure devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Ruggedcom Rox Ii FirmwareOperating system

Affected:< 2.17.0

CVSS breakdown

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?

dbcve checks

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

Identify device model

Access the device web interface or CLI and check the system information or model number. Common methods: 'show system info' command via SSH/console, or check the device label/console output at boot.

Affected if Device model is one of: MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000
Check firmware version

Execute 'show version' via CLI/SSH, or check the firmware version in the web interface under System > Firmware or About section.

Affected if Firmware version is below V2.17.0 (any version string less than 2.17.0, including V2.16.x, V2.15.x, V2.14.x, and earlier)
Verify IPsec feature status

Check IPsec configuration via CLI: 'show ipsec' or navigate to IPsec settings in the web interface under Services > IPsec. Verify if IPsec is enabled or has any active tunnels.

Affected if IPsec is enabled or any IPsec tunnels are configured on the device
Review IPsec configuration for anomalies

Examine the IPsec configuration file or output for unexpected or unauthorized IPsec profiles, keys, or remote endpoints. Check commands: 'show running-config | include ipsec' or review the ipsec.conf/ipsec.secrets files if accessible.

Affected if IPsec configuration contains unexpected profiles, unknown remote endpoints, or configuration values that were not authored by the legitimate administrator

The device is affected if it is a listed RUGGEDCOM ROX model running firmware below V2.17.0 AND has IPsec enabled or configured.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 2.17.0 or later

Fixed in 2.17.0

Interim mitigation

Upgrade RUGGEDCOM ROX firmware to version V2.17.0 or later to remediate the IPsec code injection vulnerability. Prior to upgrading, coordinate a maintenance window and backup configurations as these are critical infrastructure devices.

Recommended fix High confidence

V2.17.0 or later

1. Identify the specific Ruggedcom ROX device model (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000)
2. Check the current firmware version by accessing the device management interface
3. Navigate to the Siemens industrial support portal (cert-portal.siemens.com) and locate the firmware download for the identified device model
4. Download firmware version 2.17.0 or later for the specific device model
5. Before upgrading, backup the current device configuration according to standard procedures
6. Upload and install the firmware version 2.17.0 or later via the device's web interface or CLI, following Siemens upgrade instructions
7. After upgrade completes, verify the new firmware version is 2.17.0 or later
8. Restore the backed-up configuration if needed and verify normal device operation

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 / 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-2024-56840 — 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

Primary sources

cert-portal.siemens.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-56840 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-56840?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 2.17.0 or later

Severity 7.2 High

Exploit likelihood EPSS, next 30 days 0.6%

Affects: Ruggedcom Rox Ii Firmware

Remediation

A high-priority fix

Fix this in Ruggedcom Rox Ii Firmware 22 hrs · Moderate

Typical engagement from $3,860

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-56840 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References