CVE-2020-15799
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 · uneditedA 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). The vulnerability could allow an unauthenticated attacker to reboot the device over the network by using special urls from integrated web server of the affected products.
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 confidenceA vulnerability in the integrated web server of Siemens SCALANCE X-200 and X-200IRT switch families allows an unauthenticated attacker to cause a denial of service by rebooting the device via specially crafted URLs. The attack requires network access to the web interface but no authentication.
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< 5.5.0< 5.5.0< 5.5.0< 5.5.0< 5.5.0< 5.5.0all versionsall versionsCVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SCALANCE device modelAccess the device web interface or use SNMP to query the device. Look for the model name in the system information page or device status. The affected models are: X200 4pirt, X201 3pirt, X202 2irt, X202 2pirt, X202 2pirt Siplus Net, X204irt, X307 3, and X307 3ld.Affected if The device model is any of the SCALANCE X-200 or X-200IRT family switches listed in the affected products.
-
Check the installed firmware versionIn the device web interface, navigate to System > Information or similar page to view the firmware version. Alternatively, use the command-line interface or SNMP OID to retrieve the firmware version.Affected if The firmware version is below 5.5.0 for X200 4pirt, X201 3pirt, X202 2irt, X202 2pirt, X202 2pirt Siplus Net, or X204irt models; OR the firmware version is any version for X307 3 or X307 3ld models.
-
Verify the integrated web server is enabledIn the device web interface, navigate to the HTTP/HTTPS settings or web server configuration page. Check if the web server feature is turned on. Also verify if HTTP (port 80) or HTTPS (port 443) is listening on the device.Affected if The web server is enabled and accessible via HTTP or HTTPS on the device.
-
Confirm network accessibility to the web interfaceCheck firewall rules, VLAN configuration, and network segmentation to determine if the device web interface (ports 80/443) is reachable from untrusted network segments. Use port scanning to verify if HTTP/HTTPS ports are exposed.Affected if The device web interface is reachable from network segments where untrusted users or attackers could send HTTP requests.
A user is affected if they have any SCALANCE X-200 or X-200IRT switch from the affected list, with firmware below the safe versions, and the device web server is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 data5.5.0
Update SCALANCE X-200 devices to firmware V5.2.5 or later, and SCALANCE X-200IRT devices to V5.5.0 or later. If patching is not immediately feasible, restrict network access to the web server using firewall rules or VLAN isolation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2020-15799 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-15799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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