dbcve.org
Ruggedcom Rox Ii FirmwareOperating system · Siemens

CVE-2024-56838

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). The SCEP client available in the affected device for secure certificate enrollment lacks validation of multiple fields. 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

The SCEP (Simple Certificate Enrollment Protocol) client in RUGGEDCOM ROX MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, and RX5000 devices lacks proper validation of multiple fields during certificate enrollment. This input validation flaw allows an attacker to potentially inject and execute arbitrary code with root privileges.

MitigationUpgrade RUGGEDCOM ROX devices to firmware version V2.17.0 or later to remediate the SCEP client validation 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 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
    Locate the RUGGEDCOM device (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000) and confirm the hardware model number from the device label or web interface System Information page.
    Affected if Device is any of the listed RUGGEDCOM ROX models.
  2. Check firmware version
    Access the device web interface and navigate to System > System Information, or use the CLI command 'show version' to display the installed firmware version. Record the exact version number.
    Affected if Firmware version is below 2.17.0.
  3. Verify SCEP client is configured
    In the web interface, navigate to Certificate Management > SCEP Client (or similar path under PKI/Certificate settings). Check whether any SCEP enrollment profile is active, enabled, or configured with a CA URL.
    Affected if SCEP client is enabled or has an active enrollment configuration.
  4. Inspect SCEP certificate enrollment settings
    Review the SCEP client configuration for any manually specified fields such as Certificate Subject, SAN (Subject Alternative Name), or custom extensions. Look for editable text fields where certificate attributes can be injected.
    Affected if SCEP client allows custom field input and is actively used for certificate enrollment.

The device is affected if it is a listed RUGGEDCOM ROX model running firmware version below 2.17.0 with the SCEP client 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 RUGGEDCOM ROX devices to firmware version V2.17.0 or later to remediate the SCEP client validation vulnerability.

Recommended fix High confidence

RUGGEDCOM ROX V2.17.0

  1. 1. Obtain the V2.17.0 firmware image from the official Siemens cert-portal or Siemens support channels
  2. 2. Review the firmware release notes for any special upgrade instructions or prerequisites
  3. 3. Backup the current device configuration before proceeding with the upgrade
  4. 4. Access the RUGGEDCOM ROX device web interface or CLI management console
  5. 5. Navigate to the firmware upgrade section (typically under Administration or System > Firmware)
  6. 6. Upload the V2.17.0 firmware image to the device
  7. 7. Initiate the firmware upgrade process and allow the device to complete the update
  8. 8. After reboot, verify the device is running version V2.17.0
Caveat Review release notes for any configuration changes or feature deprecations before upgrading production devices

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

Fix this in Ruggedcom Rox Ii Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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