RUGGEDCOM ROX MX5000: Use of a Broken or Risky Cryptographic Algorithm
CVE-2023-36749 is a high-severity use of a broken or risky cryptographic algorithm vulnerability in RUGGEDCOM ROX MX5000 from Siemens, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2.16.0 as the first without the flaw, so updating RUGGEDCOM ROX MX5000 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.29% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update RUGGEDCOM ROX MX5000 to 2.16.0 or a later version.
- Update RUGGEDCOM ROX MX5000RE to 2.16.0 or a later version.
- Update RUGGEDCOM ROX RX1400 to 2.16.0 or a later version.
- Read the advisory on cert-portal.siemens.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Siemens | RUGGEDCOM ROX MX5000 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX MX5000RE | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX1400 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX1500 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX1501 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX1510 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX1511 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX1512 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX1524 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX1536 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | RUGGEDCOM ROX RX5000 | All versions < V2.16.0; before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Mx5000 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Mx5000re Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx1400 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx1500 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx1501 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx1510 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx1511 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx1512 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx1524 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx1536 Firmware | before 2.16.0 | 2.16.0 |
| Siemens | Ruggedcom Rox Rx5000 Firmware | before 2.16.0 | 2.16.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.4 | High | CNA (siemens.com) |
| CVSS 3.1 | 7.4 | High | NVD |
Official description
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 webserver of the affected devices support insecure TLS 1.0 protocol. An attacker could achieve a man-in-the-middle attack and compromise confidentiality and integrity of data.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of a Broken or Risky Cryptographic Algorithm
The product uses a broken or risky cryptographic algorithm or protocol.
How developers prevent this class of flaw
- Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms. With hardware, design the product at the Intellectual Property (IP) level so that one cryptographic algorithm can be replaced with another in the next generation of the hardware product.
- Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Industry-standard implementations will save development time and may be more likely to avoid errors that can occur during implementation of cryptographic algorithms. Consider the ESAPI Encryption feature.
More Use of a Broken or Risky Cryptographic Algorithm vulnerabilities (CWE-327)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in RUGGEDCOM ROX MX5000
- 9.1 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 7.2 High severity
- 7.2 High severity
- 7.2 High severity
Recent Use of a Broken or Risky Cryptographic Algorithm vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.