NGINX try_files vulnerability
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| F5 | NGINX Plus | unknown |
|
||||||||||||
| F5 | NGINX Open Source | unknown |
|
No data.
No data.
No data available yet.
Vendor Workaround
Avoid unnamed regex captures; use named captures instead. Do not reuse the same capture variable in other regex matches or for other purposes.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://my.f5.com/manage/s/article/K000163933 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When NGINX Plus or NGINX Open Source is configured to use the try_files and alias directives with a map variable, certain combinations of regular expression captures in map and try_files can cause a segmentation fault in an NGINX worker process. Impact: An attacker could leverage this vulnerability to cause an NGINX worker process to terminate unexpectedly. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. | |
| Title | NGINX try_files vulnerability | |
| Weaknesses | CWE-191 | |
| References |
| |
| Metrics |
cvssV3_1
|
No data.
No data.
No data.
No data.
No data.