Nginx UI: Race Condition Leads to Persistent Data Corruption and Service Collapse
0xJacky nginx-ui
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/0xJacky/Nginx-UI Go |
| No fix yet |
| github.com/uozi-tech/cosy Go |
|
|
0xJacky nginx-ui
| Product | Affected | Fixed in |
|---|---|---|
| github.com/0xJacky/Nginx-UI Go |
| No fix yet |
| github.com/uozi-tech/cosy Go |
|
|
Nginx UI is a web user interface for the Nginx web server. Prior to version 2.3.4, the nginx-ui application is vulnerable to a Race Condition. Due to the complete absence of synchronization mechanisms (Mutex) and non-atomic file writes, concurrent requests lead to the severe corruption of the primary configuration file (app.ini). This vulnerability results in a persistent Denial of Service (DoS) and introduces a non-deterministic path for Remote Code Execution (RCE) through configuration cross-contamination. This issue has been patched in version 2.3.4.
From the CVE record · GitHub_M
Before version 2.3.4, Nginx UI can corrupt its primary configuration file when concurrent requests trigger unsynchronized, non-atomic writes. This can cause a persistent denial of service and may lead to remote code execution through configuration cross-contamination. The input does not specify whether authentication is required.
Operators running Nginx UI before 2.3.4, Go package github.com/uozi-tech/cosy before 1.30.1, or github.com/0xJacky/Nginx-UI at version 1.99 or earlier should check their deployments.