# CVE-2019-12181: Command injection in n/a

> Attackers can exploit a command injection flaw in SolarWinds Serv-U for Linux to escalate privileges and execute arbitrary code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3qcp-g78m-7jv9

## What is CVE-2019-12181?

CVE-2019-12181 is a high-severity command injection vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A privilege escalation vulnerability exists in SolarWinds Serv-U before 15.1.7 for Linux.

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

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

It affects 2 products.


Products: Solarwinds Serv-U Ftp Server, Solarwinds Serv-U Mft Server.

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

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

## Is CVE-2019-12181 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-12181 exists.

Public exploit code:

- LPE Exploit For CVE-2019-12181 (Serv-U FTP 15.1.6) (github_poc): https://github.com/mavlevin/CVE-2019-12181
- Serv-U FTP Server < 15.1.7 - Local Privilege Escalation (2) (exploitdb)
- Serv-U FTP Server prepareinstallation Privilege Escalation (metasploit)
- Serv-U FTP Server < 15.1.7 - Local Privilege Escalation (1) (exploitdb)
- Serv-U FTP Server - prepareinstallation Privilege Escalation (Metasploit) (exploitdb)
- Serv-U FTP Server - prepareinstallation Privilege Escalation (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-15541](https://insights.sbomify.com/CVE-2020-15541/): Command injection in n/a (critical 9.8)
- [CVE-2020-15542](https://insights.sbomify.com/CVE-2020-15542/): Other in n/a (critical 9.8)
- [CVE-2020-15543](https://insights.sbomify.com/CVE-2020-15543/): Path traversal in n/a (critical 9.8)
- [CVE-2018-19999](https://insights.sbomify.com/CVE-2018-19999/): Auth bypass in n/a (high 7.8)
- [CVE-2018-15906](https://insights.sbomify.com/CVE-2018-15906/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12181 is a high-severity command injection vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-12181 exists.

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-12181/ (Markdown: https://insights.sbomify.com/CVE-2019-12181/index.md)
```

## Sources

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

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