dbcve.org
Scalance X200 4pirt FirmwareOperating system · Siemens

CVE-2020-15800

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-12
Fix available
A fix is available. Upgrade to 5.5.0 or later.
See remediation →
100/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 SCALANCE X-200 switch family (incl. SIPLUS NET variants) (All versions < V5.2.5), SCALANCE X-200IRT switch family (incl. SIPLUS NET variants) (All versions < V5.5.0), SCALANCE X-300 switch family (incl. X408 and SIPLUS NET variants) (All versions < V4.1.0). The webserver of the affected devices contains a vulnerability that may lead to a heap overflow condition. An attacker could cause this condition on the webserver by sending specially crafted requests. This could stop the webserver temporarily.

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

Heap overflow vulnerability in the webserver component of Siemens SCALANCE X-200, X-200IRT, and X-300 switch families. Exploitable via specially crafted HTTP requests, allowing remote attackers to crash the webserver (denial of service). CVSS 9.8 indicates trivial network exploitation without authentication.

MitigationUpdate firmware to V5.2.5 (X-200), V5.5.0 (X-200IRT), or V4.1.0 (X-300) or later. If immediate patching is not feasible, restrict network access to the device web interfaces using firewalls or VLANs.

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 X200 4pirt FirmwareOperating system
Affected:< 5.5.0
Scalance X201 3pirt FirmwareOperating system
Affected:< 5.5.0
Scalance X202 2irt FirmwareOperating system
Affected:< 5.5.0
Scalance X202 2pirt FirmwareOperating system
Affected:< 5.5.0
Scalance X202 2pirt Siplus Net FirmwareOperating system
Affected:< 5.5.0
Scalance X204irt FirmwareOperating system
Affected:< 5.5.0
Scalance X307 3 FirmwareOperating system
Affected:all versions
Scalance X307 3ld 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 SCALANCE model
    Locate the device model number on the physical device label or in the device's web interface under System > Device Information or similar. Confirm it matches one of the affected models: X200 4pirt, X201 3pirt, X202 2irt, X202 2pirt, X202 2pirt Siplus Net, X204irt, X307 3, or X307 3ld.
    Affected if The model is any of the listed affected SCALANCE X-200, X-200IRT, or X-300 variants.
  2. Determine the installed firmware version
    Access the device web interface and navigate to System > Firmware or System > Device Information to view the current firmware version. Alternatively, use the device console or management interface to query the firmware version command if available.
    Affected if The firmware version is below 5.5.0 for X-200/X-200IRT models, or any version for X307 3/X307 3ld models.
  3. Verify if the webserver component is enabled
    In the device web interface, check under Network Services > HTTP/HTTPS or similar configuration section to confirm whether the embedded webserver is currently enabled and listening on HTTP or HTTPS ports.
    Affected if The webserver is enabled and accessible on the network.
  4. Assess network exposure of the web interface
    Review network segmentation, firewall rules, or VLAN configuration to determine if the device web interface (port 80/443) is reachable from untrusted networks or the internet.
    Affected if The webserver is network-accessible beyond trusted management segments.

The environment is affected if the device is a SCALANCE X-200, X-200IRT, or X-300 model with a vulnerable firmware version and the webserver component is network-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 5.5.0 or later
Fixed in 5.5.0
Interim mitigation

Update firmware to V5.2.5 (X-200), V5.5.0 (X-200IRT), or V4.1.0 (X-300) or later. If immediate patching is not feasible, restrict network access to the device web interfaces using firewalls or VLANs.

Recommended fix High confidence

Firmware V5.5.0 or later for SCALANCE X-200IRT family; contact Siemens for X307 3/X307 3ld fix

  1. 1. Identify the exact model number of your SCALANCE X device from the device label or web interface.
  2. 2. Navigate to Siemens Industry Online Support (support.industry.siemens.com) and search for your specific device model firmware.
  3. 3. Download the latest firmware version V5.5.0 or higher for X-200IRT family devices (X200 4pirt, X201 3pirt, X202 2irt, X202 2pirt, X204irt).
  4. 4. Access the device web interface and navigate to the Firmware Update section, or use the SINEC NMS or Web Based Management (WBM) interface.
  5. 5. Upload the downloaded firmware file (.sfw or .fwf format) to the device.
  6. 6. Follow the on-screen instructions to complete the firmware update process.
  7. 7. After update, verify the firmware version in the device web interface under System > Information.
  8. 8. For X307 3 and X307 3ld models (all versions affected), contact Siemens customer support for available patches or mitigation guidance.
Caveat Review Siemens release notes for any configuration or compatibility changes before upgrading; ensure backup of device configuration

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

Fix this in Scalance X200 4pirt 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-2020-15800 — 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-2020-15800 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