dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2023-36748

MEDIUM · 6.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 2.16.0 or later.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges

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.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0), RUGGEDCOM ROX RX1400 (All versions < V2.16.0), RUGGEDCOM ROX RX1500 (All versions < V2.16.0), RUGGEDCOM ROX RX1501 (All versions < V2.16.0), RUGGEDCOM ROX RX1510 (All versions < V2.16.0), RUGGEDCOM ROX RX1511 (All versions < V2.16.0), RUGGEDCOM ROX RX1512 (All versions < V2.16.0), RUGGEDCOM ROX RX1524 (All versions < V2.16.0), RUGGEDCOM ROX RX1536 (All versions < V2.16.0), RUGGEDCOM ROX RX5000 (All versions < V2.16.0). The affected devices are configured to offer weak ciphers by default. This could allow an unauthorized attacker in a man-in-the-middle position to read and modify any data passed over to and from the affected device.

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, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) ship with weak cryptographic ciphers enabled by default. An attacker positioned man-in-the-middle can intercept and modify traffic by exploiting these weak ciphers.

MitigationUpgrade firmware to V2.16.0 or later and explicitly disable weak cipher suites in the device configuration.

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.16.0
Ruggedcom Rox Mx5000re FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1400 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1500 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1501 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1510 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1511 FirmwareOperating system
Affected:< 2.16.0
Ruggedcom Rox Rx1512 FirmwareOperating system
Affected:< 2.16.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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 access the device management interface to confirm the exact model number (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000)
    Affected if The device is one of the listed models in the CVE (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000)
  2. Check the installed firmware version
    Access the device CLI or web interface and retrieve the current firmware version. Compare it against the affected version range of < 2.16.0
    Affected if The firmware version is below 2.16.0
  3. Verify SSL/TLS protocol configuration
    Access the device management interface or configuration files and inspect the SSL/TLS settings. Look for the presence of deprecated protocols such as SSLv2, SSLv3, or TLS 1.0/1.1
    Affected if Deprecated or weak SSL/TLS protocols (SSLv2, SSLv3, TLS 1.0, TLS 1.1) are enabled
  4. Inspect enabled cipher suites
    Review the device SSL/TLS cipher configuration and check for weak or export-grade cipher suites (such as NULL, anon, or short-key ciphers)
    Affected if Weak cipher suites such as anonymous ciphers, export-grade ciphers, or ciphers with insufficient key length are enabled

A device is affected if it is a RUGGEDCOM ROX model (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, RX5000) running firmware below version 2.16.0 with weak cryptographic ciphers or deprecated SSL/TLS protocols 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.16.0 or later
Fixed in 2.16.0
Interim mitigation

Upgrade firmware to V2.16.0 or later and explicitly disable weak cipher suites in the device configuration.

Recommended fix High confidence

RUGGEDCOM ROX firmware V2.16.0

  1. Obtain the firmware version 2.16.0 or later from Siemens' official support portal (cert-portal.siemens.com) or through your standard Siemens distribution channel
  2. Review the RUGGEDCOM ROX firmware upgrade procedure in the product documentation for your specific device model
  3. Download the firmware image for your RUGGEDCOM ROX device (MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000)
  4. Follow the standard firmware upgrade process for your device (typically via web interface, CLI, or management tool)
  5. After upgrading to V2.16.0 or later, verify that weak ciphers are no longer enabled by default and that strong ciphers are configured

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

Fix this in Ruggedcom Rox Mx5000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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