# CVE-2019-10997: Denial of service in n/a

> A man-in-the-middle attacker can crash the PLC service on Phoenix Contact devices via protocol fuzzing, requiring a manual restart or reboot.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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:** 17 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-644p-jwhv-rxr7

## What is CVE-2019-10997?

CVE-2019-10997 is a medium-severity denial of service vulnerability in n/a, published on 17 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Phoenix Contact AXC F 2152 (No.2404267) before 2019.0 LTS and AXC F 2152 STARTERKIT (No.1046568) before 2019.0 LTS devices. Protocol Fuzzing on PC WORX Engineer by a man in the middle attacker stops the PLC service. The device must be rebooted, or the PLC service must be restarted manually via a Linux shell.

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

It affects 2 products.


Products: Phoenixcontact Axc F 2152 Firmware, Phoenixcontact Axc F 2152 Starterkit Firmware.

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

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

## Is CVE-2019-10997 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10998](https://insights.sbomify.com/CVE-2019-10998/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10997 is a medium-severity denial of service vulnerability in n/a, published on 17 Jun 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-10997 in the wild and no public exploit code.

Affected product: n/a. 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-10997/ (Markdown: https://insights.sbomify.com/CVE-2019-10997/index.md)
```

## Sources

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

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