# CVE-2024-22198: Authenticated (user role) arbitrary command execution by modifying `start_cmd` setting (GHSL-2023-268)

> Authenticated users can execute arbitrary commands by modifying the terminal start command setting via the API, leading to remote code execution and privilege escalation.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jan 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-8r25-68wm-jw35, GO-2024-2462

## What is CVE-2024-22198?

CVE-2024-22198 is a high-severity command injection vulnerability in 0xJacky nginx-ui, published on 11 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nginx-UI is a web interface to manage Nginx configurations. It is vulnerable to arbitrary command execution by abusing the configuration settings. The `Home > Preference` page exposes a list of system settings such as `Run Mode`, `Jwt Secret`, `Node Secret` and `Terminal Start Command`. While the UI doesn't allow users to modify the `Terminal Start Command` setting, it is possible to do so by sending a request to the API. This issue may lead to authenticated remote code execution, privilege escalation, and information disclosure. This vulnerability has been patched in version 2.0.0.beta.9.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2024-22198?

3 open source packages ship an affected version, including github.com/0xJacky/Nginx-UI. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/0xJacky/Nginx-UI` | Go | All versions | 1.9.10-0.20231219184941-827e76c46e63 |
| `github.com/0xJacky/Nginx-UI` | Go | All versions | 1.9.10-0.20231219184941-827e76c46e63 |
| `github.com/0xJacky/Nginx-UI` | Go | All versions | 1.9.10-0.20231219184941-827e76c46e63 |

Products: Nginxui Nginx Ui.

## How do I fix CVE-2024-22198?

Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20231219184941-827e76c46e63 or later.

## Is CVE-2024-22198 being exploited?

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

Public exploit code:

- Identify Nginx-ui version and check if it's vulnerable to CVE-2024-22198 (github_poc): https://github.com/xiw1ll/CVE-2024-22198_Checker

## Other vulnerabilities in 0xJacky nginx-ui

- [CVE-2026-33032](https://insights.sbomify.com/CVE-2026-33032/): Nginx UI: Unauthenticated MCP Endpoint Allows Remote Nginx Takeover (critical 9.8)
- [CVE-2026-27944](https://insights.sbomify.com/CVE-2026-27944/): Nginx UI: Unauthenticated Backup Download with Encryption Key Disclosure (critical 9.8)
- [CVE-2024-23827](https://insights.sbomify.com/CVE-2024-23827/): Nginx-UI arbitrary file write through the Import Certificate feature (critical 9.8)
- [CVE-2026-107806](https://insights.sbomify.com/CVE-2026-107806/): Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite (critical 9.4)
- [CVE-2026-33026](https://insights.sbomify.com/CVE-2026-33026/): nginx-ui Backup Restore Allows Tampering with Encrypted Backups (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22198 and fix it if it is affected.

What it is: CVE-2024-22198 is a high-severity command injection vulnerability in 0xJacky nginx-ui, published on 11 Jan 2024. 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-2024-22198 exists.

Affected packages and fixed versions:
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20231219184941-827e76c46e63
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20231219184941-827e76c46e63
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20231219184941-827e76c46e63

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

## Sources

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

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