dbcve.org
Ruggedcom Rm1224 FirmwareOperating system · Siemens

CVE-2022-31766

HIGH · 8.6 CVSS v3.1 Published 2022-10-11
Fix available
A fix is available. Upgrade to 7.1.2 or later.
See remediation →
95/100
Remediation priority · Urgent
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 RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2) (All versions < V7.1.2), RUGGEDCOM RM1224 LTE(4G) NAM (6GK6108-4AM00-2DA2) (All versions < V7.1.2), SCALANCE M804PB (6GK5804-0AP00-2AA2) (All versions < V7.1.2), SCALANCE M812-1 ADSL-Router (6GK5812-1AA00-2AA2) (All versions < V7.1.2), SCALANCE M812-1 ADSL-Router (6GK5812-1BA00-2AA2) (All versions < V7.1.2), SCALANCE M816-1 ADSL-Router (6GK5816-1AA00-2AA2) (All versions < V7.1.2), SCALANCE M816-1 ADSL-Router (6GK5816-1BA00-2AA2) (All versions < V7.1.2), SCALANCE M826-2 SHDSL-Router (6GK5826-2AB00-2AB2) (All versions < V7.1.2), SCALANCE M874-2 (6GK5874-2AA00-2AA2) (All versions < V7.1.2), SCALANCE M874-3 (6GK5874-3AA00-2AA2) (All versions < V7.1.2), SCALANCE M876-3 (6GK5876-3AA02-2BA2) (All versions < V7.1.2), SCALANCE M876-3 (ROK) (6GK5876-3AA02-2EA2) (All versions < V7.1.2), SCALANCE M876-4 (6GK5876-4AA10-2BA2) (All versions < V7.1.2), SCALANCE M876-4 (EU) (6GK5876-4AA00-2BA2) (All versions < V7.1.2), SCALANCE M876-4 (NAM) (6GK5876-4AA00-2DA2) (All versions < V7.1.2), SCALANCE MUM853-1 (EU) (6GK5853-2EA00-2DA1) (All versions < V7.1.2), SCALANCE MUM856-1 (EU) (6GK5856-2EA00-3DA1) (All versions < V7.1.2), SCALANCE MUM856-1 (RoW) (6GK5856-2EA00-3AA1) (All versions < V7.1.2), SCALANCE S615 EEC LAN-Router (6GK5615-0AA01-2AA2) (All versions < V7.1.2), SCALANCE S615 LAN-Router (6GK5615-0AA00-2AA2) (All versions < V7.1.2), SCALANCE WAM763-1 (6GK5763-1AL00-7DA0) (All versions >= V1.1.0 < V3.0.0), SCALANCE WAM766-1 (6GK5766-1GE00-7DA0) (All versions >= V1.1.0 < V3.0.0), SCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0) (All versions >= V1.1.0 < V3.0.0), SCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0) (All versions >= V1.1.0 < V3.0.0), SCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0) (All versions >= V1.1.0 < V3.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3AA0) (All versions >= V1.1.0 < V3.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3DA0) (All versions >= V1.1.0 < V3.0.0), SCALANCE WUM766-1 (6GK5766-1GE00-3DA0) (All versions >= V1.1.0 < V3.0.0), SCALANCE WUM766-1 (USA) (6GK5766-1GE00-3DB0) (All versions >= V1.1.0 < V3.0.0). Affected devices with TCP Event service enabled do not properly handle malformed packets. This could allow an unauthenticated remote attacker to cause a denial of service condition and reboot the device thus possibly affecting other network resources.

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

The vulnerability exists in the TCP Event service of Siemens RUGGEDCOM RM1224 and SCALANCE (M-series, WAM/WUM series) devices. When malformed packets are sent to the TCP Event service, it causes improper handling leading to a denial of service condition. An unauthenticated remote attacker can exploit this to cause the device to reboot, potentially affecting connected network resources.

MitigationApply vendor firmware updates to V7.1.2 or later (for RUGGEDCOM and SCALANCE M/S/Routers) or V3.0.0 or later (for SCALANCE WAM/WUM series). If updating is not immediately feasible, disable the TCP Event service if not required.

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 Rm1224 FirmwareOperating system
Affected:< 7.1.2
Scalance M804pb FirmwareOperating system
Affected:< 7.1.2
Scalance M812 1 FirmwareOperating system
Affected:< 7.1.2
Scalance M816 1 FirmwareOperating system
Affected:< 7.1.2
Scalance M826 2 FirmwareOperating system
Affected:< 7.1.2
Scalance M874 2 FirmwareOperating system
Affected:< 7.1.2
Scalance M874 3 FirmwareOperating system
Affected:< 7.1.2
Scalance M876 3 FirmwareOperating system
Affected:< 7.1.2

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Locate the device model number on the physical device label or in the device web interface under System > Device Information or similar. Confirm it matches one of: RUGGEDCOM RM1224, SCALANCE M804pb, SCALANCE M812 1, SCALANCE M816 1, SCALANCE M826 2, SCALANCE M874 2, SCALANCE M874 3, or SCALANCE M876 3.
    Affected if Device model is NOT one of the listed affected models, then this CVE does not apply.
  2. Check firmware version
    Access the device web interface or CLI and navigate to System > Firmware/Software Information, or run command 'show version' or ' firmware show'. Compare the installed firmware version against 7.1.2.
    Affected if Firmware version is 7.1.2 or higher, the vulnerability is patched. If version is below 7.1.2, the device may be affected.
  3. Verify TCP Event service status
    In the device web interface, go to Services > TCP Event or Configuration > Event Configuration > TCP Event. Check if the service is enabled. Alternatively, check via CLI with command 'show services' or 'tcp-event status'.
    Affected if TCP Event service is disabled. If disabled, the attack surface is reduced though the vulnerable code may still be present in firmware.
  4. Check network exposure of TCP Event service
    Review firewall rules, VLAN configuration, or access control lists to determine if the TCP Event service port (typically port 5431 or as configured) is exposed to untrusted network segments or the internet. Use network scan or 'netstat -an' on device if available.
    Affected if TCP Event service is only accessible from trusted management networks, the risk of remote exploitation is lower but not eliminated.

Device is affected if it is one of the listed models with firmware version below 7.1.2 AND the TCP Event service is enabled and accessible.

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 7.1.2 or later
Fixed in 7.1.2
Interim mitigation

Apply vendor firmware updates to V7.1.2 or later (for RUGGEDCOM and SCALANCE M/S/Routers) or V3.0.0 or later (for SCALANCE WAM/WUM series). If updating is not immediately feasible, disable the TCP Event service if not required.

Recommended fix High confidence

Firmware V7.1.2 or later

  1. 1. Identify all affected Ruggedcom and Scalance devices in the network using the product model numbers and firmware versions provided in the CVE advisory
  2. 2. Access each affected device's web interface or management console
  3. 3. Navigate to the firmware upgrade or system maintenance section
  4. 4. Download the fixed firmware version V7.1.2 or later from the Siemens cert-portal website (cert-portal.siemens.com)
  5. 5. Backup the current device configuration before performing the upgrade
  6. 6. Upload the V7.1.2 (or later) firmware file to the device
  7. 7. Apply the firmware upgrade and allow the device to reboot
  8. 8. After reboot, verify the new firmware version is installed correctly

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

Fix this in Ruggedcom Rm1224 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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