dbcve.org
Nginx UiWeb server / proxy · Nginxui

CVE-2024-23827

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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. The Import Certificate feature allows arbitrary write into the system. The feature does not check if the provided user input is a certification/key and allows to write into arbitrary paths in the system. It's possible to leverage the vulnerability into a remote code execution overwriting the config file app.ini. Version 2.0.0.beta.12 fixed the issue.

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's Import Certificate feature lacks proper input validation, allowing authenticated attackers to write arbitrary files to any path on the filesystem. Since the feature doesn't verify that user-supplied input is actually a certificate or key, an attacker can exploit path traversal to overwrite the app.ini configuration file and achieve remote code execution.

MitigationUpgrade to version 2.0.0.beta.12 or later. Until then, restrict access to the Import Certificate functionality and monitor for suspicious file write activity.

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:= 1.2.0= 1.2.1= 1.2.2= 1.3.0= 1.3.1= 1.3.2= 1.3.3= 1.4.0= 1.4.1= 1.4.2= 1.5.0= 1.5.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Nginx-UI is installed
    Check for Nginx-UI process or installation directory. Common locations include /usr/local/nginx-ui, /opt/nginx-ui, or check running processes for nginx-ui
    Affected if Nginx-UI is present on the system
  2. Check the installed Nginx-UI version
    Look for a version file or check the binary version: nginx-ui --version or cat version information from the UI
    Affected if Version matches 1.2.0, 1.2.1, 1.2.2, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 1.4.0, 1.4.1, 1.4.2, 1.5.0, or 1.5.1
  3. Verify Import Certificate feature access
    Check if the Import Certificate endpoint is exposed and accessible. This is typically found in the UI under the Certificates section
    Affected if The Import Certificate feature is accessible without additional access controls
  4. Inspect app.ini for unauthorized modifications
    Locate and examine the app.ini configuration file (commonly in the Nginx-UI data/config directory). Check file ownership, timestamps, and content for unexpected changes
    Affected if app.ini has been modified unexpectedly or contains suspicious content
  5. Review access logs for path traversal attempts
    Examine Nginx-UI or system logs for requests to the Import Certificate feature containing path traversal patterns like ../ or absolute paths
    Affected if Logs show Import Certificate requests with path traversal sequences

A user is affected if Nginx-UI versions 1.2.0 through 1.5.1 are running, the Import Certificate feature is accessible, and either the app.ini has been tampered with or suspicious path traversal requests appear in logs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2.0.0.beta.12 or later. Until then, restrict access to the Import Certificate functionality and monitor for suspicious file write activity.

Recommended fix High confidence

2.0.0.beta.12

  1. 1. Backup your current Nginx UI configuration and data (including app.ini and any certificates)
  2. 2. Stop the Nginx UI service
  3. 3. Upgrade Nginx UI from version 1.2.0, 1.2.1, 1.2.2, or 1.3.0 to version 2.0.0.beta.12
  4. 4. Verify the upgrade was successful by checking the version number
  5. 5. Restart the Nginx UI service
  6. 6. Validate that the Import Certificate feature now properly validates input paths
Caveat This is a major version upgrade from 1.x to 2.x which may introduce breaking changes in configuration format, API endpoints, or features - review the 2.0.0.beta.12 release notes before upgrading

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

Fix this in Nginx Ui Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23827 — 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-23827 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