# CVE-2020-25226: Memory corruption in SCALANCE X-200 switch family (incl. SIPLUS NET variants)

> An attacker can cause a denial of service on Siemens SCALANCE switches by triggering a buffer overflow in the web server via a crafted request.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p724-hcmr-xf8c

## What is CVE-2020-25226?

CVE-2020-25226 is a critical memory corruption vulnerability in Siemens SCALANCE X-200 switch family (incl. SIPLUS NET variants), published on 12 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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). 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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2020-25226?

It affects 66 products.


Products: Siemens Scalance X200-4pirt Firmware, Siemens Scalance X201-3pirt Firmware, Siemens Scalance X202-2irt Firmware, Siemens Scalance X202-2pirt Firmware, Siemens Scalance X202-2pirt Siplus Net Firmware, Siemens Scalance X204irt Firmware, Siemens Scalance X307-3 Firmware, Siemens Scalance X307-3ld Firmware, Siemens Scalance X308-2 Firmware, Siemens Scalance X308-2ld Firmware, Siemens Scalance X308-2lh\+ Firmware, Siemens Scalance X308-2lh Firmware, Siemens Scalance X308-2m Firmware, Siemens Scalance X308-2m Ts Firmware, Siemens Scalance X310 Firmware, Siemens Scalance X310fe Firmware, Siemens Scalance X320-1fe Firmware, Siemens Scalance X320-3ldfe Firmware, Siemens Scalance Xb205-3 Firmware, Siemens Scalance Xb205-3ld Firmware and 46 more.

## How do I fix CVE-2020-25226?

No fix has been published for CVE-2020-25226 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-25226 being exploited?

There is no known exploitation of CVE-2020-25226 in the wild and no public exploit code.

## Other vulnerabilities in Siemens SCALANCE X-200 switch family (incl. SIPLUS NET variants)

- [CVE-2020-15800](https://insights.sbomify.com/CVE-2020-15800/): Memory corruption in SCALANCE X-200 switch family (incl. SIPLUS NET variants) (critical 9.8)
- [CVE-2020-15799](https://insights.sbomify.com/CVE-2020-15799/): Missing authorization in SCALANCE X-200 switch family (incl. SIPLUS NET variants) (medium 6.5)
- [CVE-2020-28391](https://insights.sbomify.com/CVE-2020-28391/): Hardcoded credentials in SCALANCE X-200 switch family (incl. SIPLUS NET variants) (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-25226 and fix it if it is affected.

What it is: CVE-2020-25226 is a critical memory corruption vulnerability in Siemens SCALANCE X-200 switch family (incl. SIPLUS NET variants), published on 12 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25226 in the wild and no public exploit code.

Affected product: Siemens SCALANCE X-200 switch family (incl. SIPLUS NET variants). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-25226/ (Markdown: https://insights.sbomify.com/CVE-2020-25226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-25226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-25226
- OSV: https://osv.dev/vulnerability/CVE-2020-25226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-25226/
Summaries are generated and may contain mistakes; the official description above is the record.