dbcve.org
Ruggedcom Rox Rx1400 FirmwareOperating system · Siemens

CVE-2021-37175

MEDIUM · 5.3 CVSS v3.1 Published 2021-09-14
Fix available
A fix is available. Upgrade to 2.14.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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). The affected devices do not properly handle permissions to traverse the file system. If exploited, an attacker could gain access to an overview of the complete file system on the affected devices.

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

A detailed technical summary for this CVE is being prepared.

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 Rx1400 FirmwareOperating system
Affected:< 2.14.1
Ruggedcom Rox Mx5000 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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
Vendor patch cert-portal.siemens.com →
Recommended fix High confidence

Firmware V2.14.1 or later for Ruggedcom ROX (MX5000, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000)

  1. 1. Identify the current firmware version of the Ruggedcom ROX device by accessing the web interface or using CLI commands
  2. 2. Navigate to the Siemens Product CERT portal at https://cert-portal.siemens.com/productcert/ to obtain the firmware update V2.14.1 or later
  3. 3. Review the Siemens security advisory (ssa-150692.pdf) for specific upgrade instructions
  4. 4. Back up the current device configuration before performing the firmware upgrade
  5. 5. Upload and apply the firmware version V2.14.1 or later via the device's web management interface or TFTP method as documented in the user manual
  6. 6. After the upgrade completes, verify the device is operational and the new firmware version is installed
  7. 7. Confirm the vulnerability is remediated by testing that file system traversal permissions are properly restricted
Caveat Review Siemens release notes for V2.14.1 to check for any configuration or feature changes that may affect your deployment

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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