CVE-2023-36749: A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0)…
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 11, 2023
- Updated
- Oct 23, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-327
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.4
- CNA · siemens
- 7.4
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Check your site's encryptionRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| siemens | ruggedcom rox mx5000 firmware | cpe:2.3:o:siemens:ruggedcom_rox_mx5000_firmware |
| siemens | ruggedcom rox mx5000 | cpe:2.3:h:siemens:ruggedcom_rox_mx5000 |
| siemens | ruggedcom rox mx5000re firmware | cpe:2.3:o:siemens:ruggedcom_rox_mx5000re_firmware |
| siemens | ruggedcom rox mx5000re | cpe:2.3:h:siemens:ruggedcom_rox_mx5000re |
| siemens | ruggedcom rox rx1400 firmware | cpe:2.3:o:siemens:ruggedcom_rox_rx1400_firmware |
| siemens | ruggedcom rox rx1400 | cpe:2.3:h:siemens:ruggedcom_rox_rx1400 |
| siemens | ruggedcom rox rx1500 firmware | cpe:2.3:o:siemens:ruggedcom_rox_rx1500_firmware |
| siemens | ruggedcom rox rx1500 | cpe:2.3:h:siemens:ruggedcom_rox_rx1500 |
| siemens | ruggedcom rox rx1501 firmware | cpe:2.3:o:siemens:ruggedcom_rox_rx1501_firmware |
| siemens | ruggedcom rox rx1501 | cpe:2.3:h:siemens:ruggedcom_rox_rx1501 |
| siemens | ruggedcom rox rx1510 firmware | cpe:2.3:o:siemens:ruggedcom_rox_rx1510_firmware |
| siemens | ruggedcom rox rx1510 | cpe:2.3:h:siemens:ruggedcom_rox_rx1510 |
and 10 more
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (siemens). Independent of NVD's CPE analysis and usually ahead of it.
Siemens RUGGEDCOM ROX MX5000
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX MX5000RE
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX1400
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX1500
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX1501
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX1510
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX1511
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX1512
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX1524
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX1536
- All versions < V2.16.0affected
Siemens RUGGEDCOM ROX RX5000
- All versions < V2.16.0affected
Affected versions · NVD (11)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- siemens ruggedcom rox mx5000 firmwarebefore 2.16.0
- siemens ruggedcom rox mx5000re firmwarebefore 2.16.0
- siemens ruggedcom rox rx1400 firmwarebefore 2.16.0
- siemens ruggedcom rox rx1500 firmwarebefore 2.16.0
- siemens ruggedcom rox rx1501 firmwarebefore 2.16.0
- siemens ruggedcom rox rx1510 firmwarebefore 2.16.0
- siemens ruggedcom rox rx1511 firmwarebefore 2.16.0
- siemens ruggedcom rox rx1512 firmwarebefore 2.16.0
- siemens ruggedcom rox rx1524 firmwarebefore 2.16.0
- siemens ruggedcom rox rx1536 firmwarebefore 2.16.0
- siemens ruggedcom rox rx5000 firmwarebefore 2.16.0
Same product
siemens: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-17006In Network Security Services (NSS) before 3.46, several cryptographic primitives had missing length checks.40Plan
- CVE-2025-40949A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.17.1), RUGGEDCOM ROX MX5000RE (All versions < V2.17.1)…35Monitor
- CVE-2022-29561A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0)…35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-36386Jul 11, 2023 · A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0)…24Monitor
- ← EarlierCVE-2023-36748Jul 11, 2023 · A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0)…27Monitor
- Later →CVE-2023-36750Jul 11, 2023 · A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.0), RUGGEDCOM ROX MX5000RE (All versions < V2.16.0)…28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-327 · Use of a Broken or Risky Cryptographic AlgorithmCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Signature SpoofCAPEC-473
- Signature Spoofing by Improper ValidationCAPEC-475likelihood: Low · High
- Cryptanalysis of Cellular EncryptionCAPEC-608High
- Rooting SIM CardsCAPEC-614High
- CryptanalysisCAPEC-97likelihood: Low · Very High
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.