CVE-2024-49367
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 · uneditedNginx UI is a web user interface for the Nginx web server. Prior to version 2.0.0-beta.36, the log path of nginxui is controllable. This issue can be combined with the directory traversal at `/api/configs` to read directories and file contents on the server. Version 2.0.0-beta.36 fixes 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 confidenceNginx UI versions prior to 2.0.0-beta.36 contain a path traversal vulnerability where the log path is user-controllable and can be exploited in combination with directory traversal at the `/api/configs` endpoint to read arbitrary files and directories on the server filesystem.
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<= 1.9.9-4= 2.0.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Nginx UI installation and versionCheck the installed Nginx UI version using your package manager (e.g., `dpkg -l | grep nginx-ui`, `rpm -qa | grep nginx-ui`, or check the Docker image tag if running via container)Affected if The installed version is 1.9.9-4 or earlier, or exactly 2.0.0
-
Locate the Nginx UI configuration fileLocate the nginx-ui configuration file (commonly at `/etc/nginx-ui/admin.yaml` or within the Docker container at `/etc/nginx-ui/admin.yaml`) and inspect the `log` or `log_path` settingAffected if The log path setting is user-modifiable through the web interface at the `/api/configs` endpoint
-
Verify the web interface is accessibleConfirm the Nginx UI web interface is exposed and accessible (check nginx configuration for proxy_pass or the Docker port mapping)Affected if The `/api/configs` endpoint is reachable without additional authentication barriers beyond Nginx UI's default setup
-
Check for recent access to the configs API endpointReview Nginx UI access logs (typically found in the application data directory or system logs) for POST requests to `/api/configs` with unusual path parametersAffected if Unusual or suspicious requests to `/api/configs` with directory traversal patterns (such as `../../`) are present in logs
You are affected if Nginx UI version 1.9.9-4 or earlier, or exactly 2.0.0 is installed and the web interface with the `/api/configs` endpoint is accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Nginx UI to version 2.0.0-beta.36 or later to remediate this vulnerability.
2.0.0-beta.36
- Backup your current Nginx UI configuration and data
- Stop the Nginx UI service
- Download Nginx UI version 2.0.0-beta.36 or later from the official repository
- Install the new version following the standard installation process
- Restart the Nginx UI service
- Verify the service is running correctly and the vulnerability is fixed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49367 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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