dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2021-41546

HIGH · 7.5 CVSS v3.1 Published 2021-10-12
Fix available
A fix is available. Upgrade to 2.14.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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.14.1), RUGGEDCOM ROX RX1400 (All versions < V2.14.1), RUGGEDCOM ROX RX1500 (All versions < V2.14.1), RUGGEDCOM ROX RX1501 (All versions < V2.14.1), RUGGEDCOM ROX RX1510 (All versions < V2.14.1), RUGGEDCOM ROX RX1511 (All versions < V2.14.1), RUGGEDCOM ROX RX1512 (All versions < V2.14.1), RUGGEDCOM ROX RX1524 (All versions < V2.14.1), RUGGEDCOM ROX RX1536 (All versions < V2.14.1), RUGGEDCOM ROX RX5000 (All versions < V2.14.1). Affected devices write crashdumps without checking if enough space is available on the filesystem. Once the crashdump fills the entire root filesystem, affected devices fail to boot successfully. An attacker can leverage this vulnerability to cause a permanent Denial-of-Service.

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

RUGGEDCOM ROX devices (MX5000, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) write crashdumps without validating filesystem space availability. When the crashdump fills the root filesystem, the device cannot boot, resulting in permanent DoS.

MitigationUpgrade all affected RUGGEDCOM ROX devices to firmware version V2.14.1 or later, which includes proper space checking before crashdump writes.

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.14.1
Ruggedcom Rox Rx1400 FirmwareOperating system
Affected:< 2.14.1
Ruggedcom Rox Rx1500 FirmwareOperating system
Affected:< 2.14.1
Ruggedcom Rox Rx1501 FirmwareOperating system
Affected:< 2.14.1
Ruggedcom Rox Rx1510 FirmwareOperating system
Affected:< 2.14.1
Ruggedcom Rox Rx1511 FirmwareOperating system
Affected:< 2.14.1
Ruggedcom Rox Rx1512 FirmwareOperating system
Affected:< 2.14.1
Ruggedcom Rox Rx1524 FirmwareOperating system
Affected:< 2.14.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the RUGGEDCOM ROX device model
    Locate the device label or check the system information to confirm the model is one of: MX5000, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000
    Affected if The device is any of these models and is running vulnerable firmware
  2. Check the installed firmware version
    Access the device management interface or use the appropriate command to retrieve the current firmware version
    Affected if The firmware version is earlier than 2.14.1 (for example, 2.13.x, 2.12.x, or older)
  3. Verify crashdump functionality status
    Check the device configuration or logs to determine whether crashdump capture is enabled
    Affected if Crashdump writing is enabled on the device (this is the vulnerable feature)
  4. Inspect root filesystem space
    Check available disk space on the root filesystem using the device's diagnostic or management tools
    Affected if The root filesystem has little or no free space available

A user is affected if the device is a RUGGEDCOM ROX model running firmware version earlier than 2.14.1 with crashdump functionality enabled.

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.14.1 or later
Fixed in 2.14.1
Interim mitigation

Upgrade all affected RUGGEDCOM ROX devices to firmware version V2.14.1 or later, which includes proper space checking before crashdump writes.

Recommended fix High confidence

Firmware version V2.14.1 or later

  1. 1. Identify the specific Ruggedcom ROX device model (MX5000, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000)
  2. 2. Navigate to the Siemens cert-portal or Siemens Product Security Advisory to obtain the firmware update
  3. 3. Download firmware version V2.14.1 or later for your specific device model
  4. 4. Review the firmware upgrade instructions in the product manual or release notes
  5. 5. Back up the current device configuration if supported
  6. 6. Upload and apply the firmware version 2.14.1 or later following the manufacturer's standard upgrade procedure
  7. 7. Verify the firmware version was successfully applied and the device is operating normally
  8. 8. Confirm that crashdump functionality now properly checks filesystem space before writing
Caveat Standard firmware upgrade precautions apply - ensure stable power during upgrade and backup configuration before proceeding

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

Fix this in Ruggedcom Rox Mx5000 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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