# CVE-2024-23828: Nginx-UI authenticated RCE through injecting into the application config via CRLF

> Authenticated attackers can execute arbitrary commands by injecting CRLF sequences into Nginx-UI configuration fields.

- **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:** Yes
- **Published:** 29 Jan 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-qcjq-7f7v-pvc8, GO-2024-2480

## What is CVE-2024-23828?

CVE-2024-23828 is a high-severity command injection vulnerability in 0xJacky nginx-ui, published on 29 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 an authenticated arbitrary command execution via CRLF attack when changing the value of test_config_cmd or start_cmd. This vulnerability exists due to an incomplete fix for CVE-2024-22197 and CVE-2024-22198. This vulnerability has been patched in version 2.0.0.beta.12.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

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 | None |
| `github.com/0xJacky/Nginx-UI` | Go | All versions | 1.9.10-0.20240126104956-d70e37c8575e |
| `github.com/0xJacky/Nginx-UI` | Go | All versions | 1.9.10-0.20240126104956-d70e37c8575e |

Products: Nginxui Nginx Ui.

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

Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20240126104956-d70e37c8575e or later.

## Is CVE-2024-23828 being exploited?

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

## 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-23828 and fix it if it is affected.

What it is: CVE-2024-23828 is a high-severity command injection vulnerability in 0xJacky nginx-ui, published on 29 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23828 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/0xJacky/Nginx-UI (Go): affected all versions; no fix listed
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20240126104956-d70e37c8575e
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20240126104956-d70e37c8575e

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

## Sources

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

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