CVE-2020-25226
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 web server of the affected devices contains a vulnerability that may lead to a buffer overflow condition. An attacker could cause this condition on the webserver by sending a specially crafted request. The webserver could stop and not recover anymore.
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 confidenceBuffer overflow vulnerability in the web server component of SCALANCE X-200 and X-200IRT switch families. An unauthenticated remote attacker can send specially crafted HTTP requests to trigger the overflow, causing the webserver to crash and remain unavailable (denial of service).
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SCALANCE device modelAccess the device web interface, check the device label, or use SNMP/console to query the hardware model (for example, via 'show device' or similar management command).Affected if The device is a Scalance X200, X201, X202, X204irt, X307 3, or X307 3ld model.
-
Determine the installed firmware versionLog into the device web interface and locate the firmware version in the system information page, or use console/SNMP to query the firmware version (for example, via 'show version' or system OID).Affected if The firmware version is below 5.5.0 for X200/X200IRT models, or any version for X307 3/X307 3ld models.
-
Verify the web server component is enabledAccess the device configuration menu and check the web server settings, typically found under 'HTTP' or 'Web Server' in the network services configuration section.Affected if The web server is enabled and accessible over HTTP/HTTPS.
-
Confirm network accessibility of the web interfaceAttempt to reach the device web interface from a management station using the device IP address via HTTP (port 80) or HTTPS (port 443).Affected if The web interface responds to HTTP requests, indicating the web server is actively running.
The device is affected if it is a SCALANCE X200/X200IRT or X307 model running a vulnerable firmware version AND the web server interface is enabled and accessible on the network.
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.
dbcve · scoped5.5.0
Upgrade SCALANCE X-200 devices to firmware version V5.2.5 or higher, and SCALANCE X-200IRT devices to V5.5.0 or higher. If immediate patching is not possible, disable or restrict access to the web server interface.
Firmware version 5.5.0 for X-200IRT family; Firmware version 5.2.5 for X-200 family; latest available firmware for X307 3/X307 3ld
- 1. Identify the exact model of SCALANCE X device from the affected product list (X200 4pirt, X201 3pirt, X202 2irt, X202 2pirt, X202 2pirt Siplus Net, X204irt, X307 3, or X307 3ld)
- 2. Determine the current firmware version installed on the device via the web interface or management console
- 3. For SCALANCE X-200IRT family devices (X200 4pirt, X201 3pirt, X202 2irt, X202 2pirt, X202 2pirt Siplus Net, X204irt): download firmware version 5.5.0 or later from Siemens cert-portal.siemens.com
- 4. For SCALANCE X-200 family devices: download firmware version 5.2.5 or later from Siemens cert-portal.siemens.com
- 5. For SCALANCE X307 3 and X307 3ld: download the latest available firmware from Siemens cert-portal.siemens.com as all versions are affected
- 6. Upload the new firmware through the device's web-based management interface or via TFTP/FTP if supported
- 7. After firmware update, verify the web server is operational and the vulnerability is remediated
- 8. Consider network segmentation or disabling the web server if not required as an additional mitigation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,400.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25226 — 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-25226 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