dbcve.org
Scalance Xb208 \(e\/ip\) FirmwareOperating system · Siemens

CVE-2023-44317

HIGH · 7.2 CVSS v3.1 Published 2023-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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.2.2), RUGGEDCOM RM1224 LTE(4G) NAM (6GK6108-4AM00-2DA2) (All versions < V7.2.2), SCALANCE M804PB (6GK5804-0AP00-2AA2) (All versions < V7.2.2), SCALANCE M812-1 ADSL-Router (6GK5812-1AA00-2AA2) (All versions < V7.2.2), SCALANCE M812-1 ADSL-Router (6GK5812-1BA00-2AA2) (All versions < V7.2.2), SCALANCE M816-1 ADSL-Router (6GK5816-1AA00-2AA2) (All versions < V7.2.2), SCALANCE M816-1 ADSL-Router (6GK5816-1BA00-2AA2) (All versions < V7.2.2), SCALANCE M826-2 SHDSL-Router (6GK5826-2AB00-2AB2) (All versions < V7.2.2), SCALANCE M874-2 (6GK5874-2AA00-2AA2) (All versions < V7.2.2), SCALANCE M874-3 (6GK5874-3AA00-2AA2) (All versions < V7.2.2), SCALANCE M876-3 (6GK5876-3AA02-2BA2) (All versions < V7.2.2), SCALANCE M876-3 (ROK) (6GK5876-3AA02-2EA2) (All versions < V7.2.2), SCALANCE M876-4 (6GK5876-4AA10-2BA2) (All versions < V7.2.2), SCALANCE M876-4 (EU) (6GK5876-4AA00-2BA2) (All versions < V7.2.2), SCALANCE M876-4 (NAM) (6GK5876-4AA00-2DA2) (All versions < V7.2.2), SCALANCE MUM853-1 (EU) (6GK5853-2EA00-2DA1) (All versions < V7.2.2), SCALANCE MUM856-1 (EU) (6GK5856-2EA00-3DA1) (All versions < V7.2.2), SCALANCE MUM856-1 (RoW) (6GK5856-2EA00-3AA1) (All versions < V7.2.2), SCALANCE S615 EEC LAN-Router (6GK5615-0AA01-2AA2) (All versions < V7.2.2), SCALANCE S615 LAN-Router (6GK5615-0AA00-2AA2) (All versions < V7.2.2), SCALANCE WAB762-1 (6GK5762-1AJ00-6AA0) (All versions < V3.0.0), SCALANCE WAM763-1 (6GK5763-1AL00-7DA0) (All versions < V3.0.0), SCALANCE WAM763-1 (ME) (6GK5763-1AL00-7DC0) (All versions < V3.0.0), SCALANCE WAM763-1 (US) (6GK5763-1AL00-7DB0) (All versions < V3.0.0), SCALANCE WAM766-1 (6GK5766-1GE00-7DA0) (All versions < V3.0.0), SCALANCE WAM766-1 (ME) (6GK5766-1GE00-7DC0) (All versions < V3.0.0), SCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (ME) (6GK5766-1GE00-7TC0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0) (All versions < V3.0.0), SCALANCE WUB762-1 (6GK5762-1AJ00-1AA0) (All versions < V3.0.0), SCALANCE WUB762-1 iFeatures (6GK5762-1AJ00-2AA0) (All versions < V3.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3AA0) (All versions < V3.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3DA0) (All versions < V3.0.0), SCALANCE WUM763-1 (US) (6GK5763-1AL00-3AB0) (All versions < V3.0.0), SCALANCE WUM763-1 (US) (6GK5763-1AL00-3DB0) (All versions < V3.0.0), SCALANCE WUM766-1 (6GK5766-1GE00-3DA0) (All versions < V3.0.0), SCALANCE WUM766-1 (ME) (6GK5766-1GE00-3DC0) (All versions < V3.0.0), SCALANCE WUM766-1 (USA) (6GK5766-1GE00-3DB0) (All versions < V3.0.0). Affected products do not properly validate the content of uploaded X509 certificates which could allow an attacker with administrative privileges to execute arbitrary code on the device.

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 multiple Siemens RUGGEDCOM and SCALANCE industrial networking devices. Affected firmware versions fail to properly validate the content of uploaded X509 certificates. An attacker who already possesses administrative privileges can upload a specially crafted malicious certificate that triggers arbitrary code execution on the device, leading to full compromise of the network device.

MitigationUpgrade affected devices to the patched versions (V7.2.2 for routers/modems, V3.0.0 for wireless products). Restrict administrative access to trusted personnel and monitor for unauthorized certificate uploads.

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
Scalance Xb208 \(e\/ip\) FirmwareOperating system
Affected:all versions
Scalance Xb208 \(pn\) FirmwareOperating system
Affected:all versions
Scalance Xb216 \(e\/ip\) FirmwareOperating system
Affected:all versions
Scalance Xb216 \(pn\) FirmwareOperating system
Affected:all versions
Scalance Xc206 2 \(sc\) FirmwareOperating system
Affected:all versions
Scalance Xc206 2 \(st\/bfoc\) FirmwareOperating system
Affected:all versions
Scalance Xc206 2g Poe FirmwareOperating system
Affected:all versions
Scalance Xc206 2g Poe \(54 V Dc\) FirmwareOperating system
Affected:all versions

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
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 checks

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

  1. Identify the device model
    Access the device web interface or CLI and record the exact model name (e.g., Scalance Xb208, Xb216, Xc206-2). Compare against the list of affected models.
    Affected if The device is a Scalance Xb208, Xb216, or Xc206-2 variant (any sub-model).
  2. Check the firmware version
    In the device web interface, navigate to System > Firmware or use the CLI command 'show firmware version' or 'sysinfo'. Record the installed version number.
    Affected if The device is one of the affected models regardless of firmware version, as all versions are listed as vulnerable.
  3. Verify admin web interface accessibility
    Attempt to access the device web management interface (HTTP/HTTPS on ports 80/443 or custom ports). Check if the interface is reachable from network segments outside the trusted management network.
    Affected if The administrative web interface is exposed to untrusted networks, allowing an attacker with admin credentials to reach the certificate upload function.
  4. Locate the certificate management function
    In the device web UI, navigate to System > Certificates, Security > Certificate Management, or similar. Identify whether a certificate upload or import feature exists.
    Affected if The certificate upload/import feature is present and accessible to administrative users.
  5. Review installed certificates
    In the certificate management section, list all uploaded or installed certificates. Check for unknown, self-signed, or suspiciously named certificates that were not intentionally deployed.
    Affected if Unexpected or unrecognized certificates are installed on the device.

A user is affected if they operate any Scalance Xb208, Xb216, or Xc206-2 device with the administrative web interface accessible to potential attackers, since all firmware versions of these models lack proper X509 certificate validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade affected devices to the patched versions (V7.2.2 for routers/modems, V3.0.0 for wireless products). Restrict administrative access to trusted personnel and monitor for unauthorized certificate uploads.

Recommended fix High confidence

V7.2.2 for M-series/RUGGEDCOM devices; V3.0.0 for W-series devices

  1. 1. Identify the specific SCALANCE device model and variant from the affected product list
  2. 2. For SCALANCE M-series devices (M804PB, M812-1, M816-1, M826-2, M874-2, M874-3, M876-3, M876-4, MUM853-1, MUM856-1, S615), upgrade firmware to version V7.2.2 or later
  3. 3. For SCALANCE W-series devices (WAB762-1, WAM763-1, WAM766-1, WUB762-1, WUM763-1, WUM766-1), upgrade firmware to version V3.0.0 or later
  4. 4. For RUGGEDCOM RM1224 devices, upgrade firmware to version V7.2.2 or later
  5. 5. After upgrade, verify the device is running the patched firmware version
  6. 6. If upgrade is not immediately possible, restrict administrative access to trusted personnel only and monitor for unauthorized certificate uploads
  7. 7. Ensure only X509 certificates from trusted sources are uploaded to the device
Caveat Review release notes for any configuration or compatibility changes between current version and target version

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

Fix this in Scalance Xb208 \(e\/ip\) Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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