# CVE-2023-38380: Memory corruption in SIMATIC CP 1242-7 V2 (incl. SIPLUS variants)

> A memory leak in the webserver allows remote attackers to cause a denial-of-service condition in Siemens SIMATIC communication processors.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-532g-fpxj-7pxx

## What is CVE-2023-38380?

CVE-2023-38380 is a high-severity memory corruption vulnerability in Siemens SIMATIC CP 1242-7 V2 (incl. SIPLUS variants), published on 12 Dec 2023. 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 SIMATIC CP 1242-7 V2 (incl. SIPLUS variants) (All versions < V3.4.29), SIMATIC CP 1243-1 (incl. SIPLUS variants) (All versions < V3.4.29), SIMATIC CP 1243-1 DNP3 (incl. SIPLUS variants) (All versions), SIMATIC CP 1243-1 IEC (incl. SIPLUS variants) (All versions < V3.4.29), SIMATIC CP 1243-7 LTE (All versions < V3.4.29), SIMATIC CP 1243-8 IRC (6GK7243-8RX30-0XE0) (All versions < V3.4.29), SIMATIC CP 1542SP-1 (6GK7542-6UX00-0XE0) (All versions < V2.3), SIMATIC CP 1542SP-1 IRC (6GK7542-6VX00-0XE0) (All versions < V2.3), SIMATIC CP 1543-1 (6GK7543-1AX00-0XE0) (All versions < V3.0.37), SIMATIC CP 1543SP-1 (6GK7543-6WX00-0XE0) (All versions < V2.3), SINAMICS S210 (6SL5...) (All versions >= V6.1 < V6.1 HF2), SIPLUS ET 200SP CP 1542SP-1 IRC TX RAIL (6AG2542-6VX00-4XE0) (All versions < V2.3), SIPLUS ET 200SP CP 1543SP-1 ISEC (6AG1543-6WX00-7XE0) (All versions < V2.3), SIPLUS ET 200SP CP 1543SP-1 ISEC TX RAIL (6AG2543-6WX00-4XE0) (All versions < V2.3), SIPLUS NET CP 1543-1 (6AG1543-1AX00-2XE0) (All versions < V3.0.37). The webserver implementation of the affected products does not correctly release allocated memory after it has been used.

An attacker with network access could use this vulnerability to cause a denial-of-service condition in the webserver of the affected product.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 9 products.


Products: Siemens 6ag1543-1ax00-2xe0 Firmware, Siemens 6gk7243-8rx30-0xe0 Firmware, Siemens 6gk7543-1ax00-0xe0 Firmware, Siemens Simatic Cp 1242-7 V2 Firmware, Siemens Simatic Cp 1243-1 Dnp3 Firmware, Siemens Simatic Cp 1243-1 Firmware, Siemens Simatic Cp 1243-1 Iec Firmware, Siemens Simatic Cp 1243-7 Lte Firmware, Siemens Sinamics S210 Firmware.

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

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

## Is CVE-2023-38380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38380 is a high-severity memory corruption vulnerability in Siemens SIMATIC CP 1242-7 V2 (incl. SIPLUS variants), published on 12 Dec 2023. 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-2023-38380 in the wild and no public exploit code.

Affected product: Siemens SIMATIC CP 1242-7 V2 (incl. SIPLUS 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-2023-38380/ (Markdown: https://insights.sbomify.com/CVE-2023-38380/index.md)
```

## Sources

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

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