# CVE-2023-29054: Weak cryptography in SCALANCE X200-4P IRT

> Weak SSH ciphers in Siemens SCALANCE switches allow man-in-the-middle attackers to read and modify network traffic.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H/E:P/RL:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Apr 2023
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-6488-g94h-5jh6

## What is CVE-2023-29054?

CVE-2023-29054 is a medium-severity vulnerability in Siemens SCALANCE X200-4P IRT, published on 11 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in SCALANCE X200-4P IRT (All versions < V5.5.2), SCALANCE X201-3P IRT (All versions < V5.5.2), SCALANCE X201-3P IRT PRO (All versions < V5.5.2), SCALANCE X202-2IRT (All versions < V5.5.2), SCALANCE X202-2IRT (All versions < V5.5.2), SCALANCE X202-2P IRT (All versions < V5.5.2), SCALANCE X202-2P IRT PRO (All versions < V5.5.2), SCALANCE X204IRT (All versions < V5.5.2), SCALANCE X204IRT (All versions < V5.5.2), SCALANCE X204IRT PRO (All versions < V5.5.2), SCALANCE XF201-3P IRT (All versions < V5.5.2), SCALANCE XF202-2P IRT (All versions < V5.5.2), SCALANCE XF204-2BA IRT (All versions < V5.5.2), SCALANCE XF204IRT (All versions < V5.5.2), SIPLUS NET SCALANCE X202-2P IRT (All versions < V5.5.2). The SSH server on affected devices is configured to offer weak ciphers by default.

This could allow an unauthorized attacker in a man-in-the-middle position to read and modify any data
passed over the connection between legitimate clients and the affected device.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2023-29054?

It affects 13 products.


Products: Siemens Scalance X200-4p Irt Firmware, Siemens Scalance X201-3p Irt Firmware, Siemens Scalance X201-3p Irt Pro Firmware, Siemens Scalance X202-2irt Firmware, Siemens Scalance X202-2p Irt Firmware, Siemens Scalance X202-2p Irt Pro Firmware, Siemens Scalance X204irt Firmware, Siemens Scalance X204irt Pro Firmware, Siemens Scalance Xf201-3p Irt Firmware, Siemens Scalance Xf202-2p Irt Firmware, Siemens Scalance Xf204-2ba Irt Firmware, Siemens Scalance Xf204irt Firmware, Siemens Siplus Net Scalance X202-2p Irt Firmware.

## How do I fix CVE-2023-29054?

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

## Is CVE-2023-29054 being exploited?

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

## Other vulnerabilities in Siemens SCALANCE X200-4P IRT

- [CVE-2021-25668](https://insights.sbomify.com/CVE-2021-25668/): Memory corruption in SCALANCE X200-4P IRT (critical 9.8)
- [CVE-2021-25669](https://insights.sbomify.com/CVE-2021-25669/): Memory corruption in SCALANCE X200-4P IRT (critical 9.8)
- [CVE-2022-26649](https://insights.sbomify.com/CVE-2022-26649/): Denial of service in SCALANCE X200-4P IRT (critical 9.6)
- [CVE-2022-26647](https://insights.sbomify.com/CVE-2022-26647/): Weak cryptography in SCALANCE X200-4P IRT (high 8.8)
- [CVE-2022-26648](https://insights.sbomify.com/CVE-2022-26648/): Denial of service in SCALANCE X200-4P IRT (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29054 and fix it if it is affected.

What it is: CVE-2023-29054 is a medium-severity vulnerability in Siemens SCALANCE X200-4P IRT, published on 11 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-29054 in the wild and no public exploit code.

Affected product: Siemens SCALANCE X200-4P IRT. 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-2023-29054/ (Markdown: https://insights.sbomify.com/CVE-2023-29054/index.md)
```

## Sources

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

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