CVE-2023-36750
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 · uneditedA 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 software-upgrade Url parameter in the web interface of affected devices is vulnerable to command injection due to missing server side input sanitation. This could allow an authenticated privileged remote attacker to execute arbitrary code with root privileges.
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 confidenceCommand injection vulnerability in the software-upgrade URL parameter of the RUGGEDCOM ROX web interface. Missing server-side input sanitization allows an authenticated privileged attacker to inject arbitrary shell commands that execute with root privileges.
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< 2.16.0< 2.16.0< 2.16.0< 2.16.0< 2.16.0< 2.16.0< 2.16.0< 2.16.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Ruggedcom ROX device modelAccess the device console, CLI, or web interface and locate the model identifier. Affected models include: Mx5000, Mx5000re, Rx1400, Rx1500, Rx1501, Rx1510, Rx1511, or Rx1512.Affected if The device is one of these eight listed models and is running the vulnerable firmware.
-
Determine the installed firmware versionIn the device web interface, navigate to System Information or About. Alternatively, use the CLI command 'show version' to retrieve the firmware version number.Affected if The firmware version is below 2.16.0 (for example, 2.15.x or earlier).
-
Confirm the web interface is enabledCheck if the HTTP or HTTPS web interface is accessible on the device by attempting to reach the device IP address in a browser or checking the network service configuration.Affected if The web interface is enabled and reachable, since the command injection occurs in the software-upgrade URL parameter.
-
Verify administrative accounts existCheck if any privileged user accounts are configured on the device, as the vulnerability requires an authenticated privileged attacker.Affected if Administrative or privileged user accounts are present on the device.
The environment is affected if the device is a Ruggedcom ROX model (Mx5000/Mx5000re/Rx1400/Rx1500/Rx1501/Rx1510/Rx1511/Rx1512) running firmware below version 2.16.0 with the web interface enabled and administrative access configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.16.0
Upgrade RUGGEDCOM ROX devices to firmware version V2.16.0 or later to patch the command injection vulnerability. Restrict administrative access to trusted personnel only.
V2.16.0
- Obtain the firmware version V2.16.0 for your specific Ruggedcom ROX device from Siemens (cert-portal.siemens.com)
- Back up the current device configuration before proceeding with the upgrade
- Access the device web interface and navigate to the software upgrade functionality
- Upload and apply firmware version V2.16.0 to the device
- After the upgrade completes, verify the device is running version V2.16.0
- Confirm the software-upgrade URL parameter now properly sanitizes input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-36750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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