dbcve.org
Ruggedcom Rox Mx5000 FirmwareOperating system · Siemens

CVE-2022-29562

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

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). Affected devices do not properly handle malformed HTTP packets. This could allow an unauthenticated remote attacker to send a malformed HTTP packet causing certain functions to fail in a controlled manner.

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) versions prior to V2.16.0 contain a vulnerability in HTTP packet handling. An unauthenticated remote attacker can send malformed HTTP packets to cause certain device functions to fail in a controlled manner, resulting in denial of service or disrupted operations.

MitigationUpgrade RUGGEDCOM ROX firmware to version V2.16.0 or later to remediate the malformed HTTP packet handling vulnerability.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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

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
    Check the device label, web interface (typically under Status or Device Info), or use CLI command 'show version' to confirm the exact model number
    Affected if Model is one of MX5000, MX5000RE, RX1400, RX1500, RX1501, RX1510, RX1511, RX1512, RX1524, RX1536, or RX5000
  2. Determine the installed firmware version
    Access the web interface and navigate to System > Version or System Information, or use CLI command 'show version' to display the firmware version
    Affected if Firmware version is below 2.16.0 or the version cannot be confirmed as 2.16.0 or higher
  3. Verify HTTP web interface is accessible
    Attempt to reach the device web interface via HTTP (port 80) or HTTPS (port 443) from the network segment in question, or check device network configuration for HTTP service status
    Affected if HTTP/HTTPS service is enabled and reachable from network locations where an unauthenticated attacker could send packets

The device is affected if it is a RUGGEDCOM ROX model from the list, running firmware version lower than 2.16.0, with the HTTP web interface exposed to the network.

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 RUGGEDCOM ROX firmware to version V2.16.0 or later to remediate the malformed HTTP packet handling vulnerability.

Recommended fix High confidence

V2.16.0

  1. 1. Identify all affected Ruggedcom ROX devices in the network inventory
  2. 2. Download the V2.16.0 firmware or later from Siemens cert-portal.siemens.com or the Siemens Product Security Advisory
  3. 3. Review the device upgrade documentation for proper firmware update procedures
  4. 4. Schedule a maintenance window to minimize operational impact
  5. 5. Back up current device configuration before performing the upgrade
  6. 6. Upload and install the V2.16.0 firmware to each affected device
  7. 7. Verify the firmware version has been successfully updated to V2.16.0 or later
  8. 8. Test that device functionality is operational and the HTTP handling vulnerability is remediated
Caveat Review Siemens release notes for V2.16.0 to check for any configuration or feature changes that may affect existing deployments

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

Fix this in Ruggedcom Rox Mx5000 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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