# CVE-2019-5029: Command injection in Exhibitor

> Attackers can execute arbitrary shell commands via the Exhibitor Web UI Config editor, compromising the server running ZooKeeper.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 13 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vq4h-pfrp-qjjj

## What is CVE-2019-5029?

CVE-2019-5029 is a critical command injection vulnerability in Exhibitor, published on 13 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable command injection vulnerability exists in the Config editor of the Exhibitor Web UI versions 1.0.9 to 1.7.1. Arbitrary shell commands surrounded by backticks or $() can be inserted into the editor and will be executed by the Exhibitor process when it launches ZooKeeper. An attacker can execute any command as the user running the Exhibitor process.

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

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

It affects 1 product.


Products: Exhibitor Project Exhibitor.

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

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

## Is CVE-2019-5029 being exploited?

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

Public exploit code:

- Exihibitor Web Ui 1.7.1 RCE, CVE-2019-5029 (github_poc): https://github.com/thehunt1s0n/Exihibitor-RCE
- Exhibitor Web UI 1.7.1 - Remote Code Execution (exploitdb)
- This is a Python script PoC for CVE-2019-5029 (github_poc): https://github.com/yZee00/CVE-2019-5029

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5029 is a critical command injection vulnerability in Exhibitor, published on 13 Nov 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-5029 in the wild and no public exploit code.

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

## Sources

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

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