# CVE-2019-13927: Denial of service in Desigo PX automation controllers PXC00-E.D, PXC50-E.D, PXC100-E.D, PXC200-E.D with Desigo PX Web modules PXA40-W0, PXA40-W1, PXA40-W2

> An attacker can cause a denial of service on the web server of Siemens Desigo PX automation controllers by sending a specially crafted HTTP message.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **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 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3phq-67rm-2hq8

## What is CVE-2019-13927?

CVE-2019-13927 is a medium-severity denial of service vulnerability in Siemens AG Desigo PX automation controllers PXC00-E.D, PXC50-E.D, PXC100-E.D, PXC200-E.D with Desigo PX Web modules PXA40-W0, PXA40-W1, PXA40-W2, published on 12 Dec 2019. 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 Desigo PX automation controllers PXC00-E.D, PXC50-E.D, PXC100-E.D, PXC200-E.D with Desigo PX Web modules PXA40-W0, PXA40-W1, PXA40-W2 (All firmware versions < V6.00.320), Desigo PX automation controllers PXC00-U, PXC64-U, PXC128-U with Desigo PX Web modules PXA30-W0, PXA30-W1, PXA30-W2 (All firmware versions < V6.00.320), Desigo PX automation controllers PXC22.1-E.D, PXC36-E.D, PXC36.1-E.D with activated web server (All firmware versions < V6.00.320). The device contains a vulnerability that could allow an attacker to cause a denial of service condition on the device's web server by sending a specially crafted HTTP message to the web server port (tcp/80). The security vulnerability could be exploited by an attacker with network access to an affected device. Successful exploitation requires no system privileges and no user interaction. An attacker could use the vulnerability to compromise the availability of the device's web service. While the device itself stays operational, the web server responds with HTTP status code 404 (Not found) to any further request. A reboot is required to recover the web interface. At the time of advisory publication no public exploitation of this security vulnerability was known.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-472 (External Control of Assumed-Immutable Web Parameter)

## Which versions are affected by CVE-2019-13927?

It affects 16 products.


Products: Siemens Pxa30-W0 Firmware, Siemens Pxa30-W1 Firmware, Siemens Pxa30-W2 Firmware, Siemens Pxa40-W0 Firmware, Siemens Pxa40-W1 Firmware, Siemens Pxa40-W2 Firmware, Siemens Pxc00-E.d Firmware, Siemens Pxc00-U Firmware, Siemens Pxc100-E.d Firmware, Siemens Pxc128-U Firmware, Siemens Pxc200-E.d Firmware, Siemens Pxc22.1-E.d Firmware, Siemens Pxc36-E.d Firmware, Siemens Pxc36.1-E.d Firmware, Siemens Pxc50-E.d Firmware, Siemens Pxc64-U Firmware.

## How do I fix CVE-2019-13927?

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

## Is CVE-2019-13927 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13927 and fix it if it is affected.

What it is: CVE-2019-13927 is a medium-severity denial of service vulnerability in Siemens AG Desigo PX automation controllers PXC00-E.D, PXC50-E.D, PXC100-E.D, PXC200-E.D with Desigo PX Web modules PXA40-W0, PXA40-W1, PXA40-W2, published on 12 Dec 2019. 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-2019-13927 in the wild and no public exploit code.

Affected product: Siemens AG Desigo PX automation controllers PXC00-E.D, PXC50-E.D, PXC100-E.D, PXC200-E.D with Desigo PX Web modules PXA40-W0, PXA40-W1, PXA40-W2. 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-2019-13927/ (Markdown: https://insights.sbomify.com/CVE-2019-13927/index.md)
```

## Sources

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

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