Scalance X408 FirmwareOperating system · Siemens

CVE-2018-13807

HIGH · 8.6 CVSS v3.0 Published 2018-09-12
Fix available
A fix is available. Upgrade to 4.0.0 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 SCALANCE X300 (All versions < V4.0.0), SCALANCE X408 (All versions < V4.0.0), SCALANCE X414 (All versions). The web interface on port 443/tcp could allow an attacker to cause a Denial-of-Service condition by sending specially crafted packets to the web server. The device will automatically reboot, impacting network availability for other devices. An attacker must have network access to port 443/tcp to exploit the vulnerability. Neither valid credentials nor interaction by a legitimate user is required to exploit the vulnerability. There is no confidentiality or integrity impact, only availability is temporarily impacted. This vulnerability could be triggered by publicly available tools.

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

A denial-of-service vulnerability in the web interface (port 443/tcp) of Siemens SCALANCE X300, X408, and X414 industrial network switches allows an unauthenticated remote attacker to cause device reboot by sending specially crafted packets, impacting network availability.

MitigationUpgrade SCALANCE X300/X408 firmware to V4.0.0 or later (X414 has no fix available); as interim measure, restrict network access to port 443/tcp via firewall or VLAN segmentation.

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 X408 FirmwareOperating system
Affected:< 4.0.0
Scalance X300 FirmwareOperating system
Affected:< 4.0.0
Scalance X414 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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/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 the SCALANCE device model
    Access the device web interface or use SNMP to query the device sysDescr. Alternatively, check the physical device label or management interface for the exact model number (X300, X408, or X414).
    Affected if The device is a SCALANCE X300, X408, or X414 model.
  2. Determine the firmware version
    Log into the web interface and navigate to System > Information > Firmware Version, or use the command-line interface and run the 'show firmware version' or equivalent command.
    Affected if The installed firmware version is less than 4.0.0 for X300 or X408, or any version for X414.
  3. Verify the web interface is enabled
    Check the device configuration for HTTP/HTTPS web server settings. This is typically found under 'HTTP' or 'Web Based Management' in the device settings. Confirm port 443 is listening by attempting a connection or using a network scanner.
    Affected if The web interface on port 443/tcp is enabled and accessible.
  4. Assess network exposure of port 443
    Review firewall rules, VLAN configuration, or network segmentation to determine if port 443/tcp on the SCALANCE device is reachable from untrusted networks or the internet.
    Affected if Port 443/tcp is exposed to untrusted networks or attacker-accessible locations.

A user is affected if they have a SCALANCE X300 or X408 with firmware below V4.0.0, or any X414 model, with the web interface on port 443 enabled and accessible from the network where an attacker could send malicious packets.

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.

From vendor data
Upgrade available Upgrade to 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Upgrade SCALANCE X300/X408 firmware to V4.0.0 or later (X414 has no fix available); as interim measure, restrict network access to port 443/tcp via firewall or VLAN segmentation.

Fix this in Scalance X408 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
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,760.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13807 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-13807 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