# CVE-2019-5167: Command injection in WAGO PFC200 Firmware

> Attackers can execute arbitrary commands on WAGO PFC200 devices by injecting malicious DNS entries into an XML configuration file.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9mfc-vm32-v9f4

## What is CVE-2019-5167?

CVE-2019-5167 is a high-severity command injection vulnerability in WAGO PFC200 Firmware, published on 10 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An exploitable command injection vulnerability exists in the iocheckd service ‘I/O-Check’ function of the WAGO PFC 200 version 03.02.02(14). At 0x1e3f0 the extracted dns value from the xml file is used as an argument to /etc/config-tools/edit_dns_server %s dns-server-nr=%d dns-server-name=<contents of dns node> using sprintf(). This command is later executed via a call to system(). This is done in a loop and there is no limit to how many dns entries will be parsed from the xml file.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Wago Pfc200 Firmware.

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

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

## Is CVE-2019-5167 being exploited?

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

## Other vulnerabilities in WAGO PFC200 Firmware

- [CVE-2018-5459](https://insights.sbomify.com/CVE-2018-5459/): Auth bypass in WAGO PFC200 Series (critical 9.8)
- [CVE-2019-5160](https://insights.sbomify.com/CVE-2019-5160/): Server-side request forgery in WAGO PFC200 Firmware (critical 9.1)
- [CVE-2019-5161](https://insights.sbomify.com/CVE-2019-5161/): Code injection in WAGO PFC200 Firmware (critical 9.1)
- [CVE-2019-5184](https://insights.sbomify.com/CVE-2019-5184/): Use after free in Wago (high 7.8)
- [CVE-2019-5169](https://insights.sbomify.com/CVE-2019-5169/): Command injection in WAGO PFC200 (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5167 is a high-severity command injection vulnerability in WAGO PFC200 Firmware, published on 10 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-5167 in the wild and no public exploit code.

Affected product: WAGO PFC200 Firmware. 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-5167/ (Markdown: https://insights.sbomify.com/CVE-2019-5167/index.md)
```

## Sources

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

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