dbcve.org
Nginx UiWeb server / proxy · Nginxui

CVE-2024-23828

HIGH · 8.8 CVSS v3.1 Published 2024-01-29
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Nginx-UI versions prior to 2.0.0.beta.12 contain an authenticated command injection vulnerability via CRLF injection in the test_config_cmd and start_cmd parameters. An authenticated attacker can inject arbitrary commands by manipulating these configuration values, achieving remote code execution on the host system.

MitigationUpgrade Nginx-UI to version 2.0.0.beta.12 or later. If immediate patching is not possible, restrict administrative access to trusted users and monitor for suspicious config parameter modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nginx UiWeb server / proxy
Affected:< 2.0.0= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Nginx-UI installed version
    Run 'nginx-ui -v' or check the Docker container image tag, or look at the binary/package version
    Affected if The installed version is any version prior to 2.0.0.beta.12, or exactly 2.0.0
  2. Locate the Nginx-UI configuration file
    Find the configuration file typically located at /etc/nginx-ui/nginx-ui.yaml or ~/nginx-ui.yaml, or the Docker config mount point
    Affected if A configuration file exists and contains test_config_cmd or start_cmd parameters
  3. Inspect test_config_cmd parameter
    Open the configuration file and search for 'test_config_cmd' - verify if this parameter is defined and contains custom command values
    Affected if The parameter exists with non-default or injectable values
  4. Inspect start_cmd parameter
    Open the configuration file and search for 'start_cmd' - verify if this parameter is defined and contains custom command values
    Affected if The parameter exists with non-default or injectable values
  5. Verify admin interface accessibility
    Check if the Nginx-UI admin panel is exposed externally or accessible without proper access controls by reviewing web server config and firewall rules
    Affected if The admin interface is accessible from untrusted networks or users

You are affected if your Nginx-UI version is before 2.0.0.beta.12 (or exactly 2.0.0) AND the admin interface is accessible to untrusted users, especially if test_config_cmd or start_cmd parameters are configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Upgrade Nginx-UI to version 2.0.0.beta.12 or later. If immediate patching is not possible, restrict administrative access to trusted users and monitor for suspicious config parameter modifications.

Recommended fix High confidence

2.0.0 or later stable release (or 2.0.0.beta.12+ if using beta channel)

  1. 1. Back up your current Nginx-UI configuration and data directory
  2. 2. Check your current installed version using the application's version endpoint or CLI command
  3. 3. Consult the project's GitHub releases page (github.com/0xERR0R/nginx-ui/releases) to identify the latest stable version after 2.0.0
  4. 4. Download the appropriate package for your platform (Linux amd64, arm64, darwin, etc.)
  5. 5. Stop the nginx-ui service
  6. 6. Replace the binary or update via your package manager (docker, helm, etc.)
  7. 7. Start the nginx-ui service
  8. 8. Verify the upgrade was successful by checking the version
Caveat Review release notes between your current version and target version for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nginx Ui Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23828 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23828 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data