Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 0xJacky | nginx-ui | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 0xjacky | Nginx-ui |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wq4w-vwvq-q3x9 | Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.210% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
0xjacky
0xjacky nginx-ui |
|
| Vendors & Products |
0xjacky
0xjacky nginx-ui |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, GenerateShortToken creates standalone short-token records without a long Token value, but DeleteUserTokens invalidates cached entries only when the long Token field is nonempty. A revoked short token can therefore remain in the short_token cache and authenticate again if the associated account is re-enabled before the cache entry expires because GetTokenUserByShortToken reads the surviving entry, restoring access to HTTP or WebSocket routes that accept short-token authentication. This issue is fixed in version 2.4.1. | |
| Title | Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable | |
| Weaknesses | CWE-613 | |
| References |
| |
| Metrics |
cvssV3_1
|