NGINX Open Source and NGINX Plus have a vulnerability in the ngx_http_dav_module module that might allow an attacker to trigger a buffer overflow to the NGINX worker process; this vulnerability may result in termination of the NGINX worker process or modification of source or destination file names outside the document root. This issue affects NGINX Open Source and NGINX Plus when the configuration file uses DAV module MOVE or COPY methods, prefix location (nonregular expression location configuration), and alias directives. The integrity impact is constrained because the NGINX worker process user has low privileges and does not have access to the entire system. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Weakness
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Nginx_plus | F5 | r32-p1 (including) | r32-p1 (including) |
| Nginx_plus | F5 | r32-p2 (including) | r32-p2 (including) |
| Nginx_plus | F5 | r32-p3 (including) | r32-p3 (including) |
| Nginx_plus | F5 | r32-p4 (including) | r32-p4 (including) |
| Nginx_plus | F5 | r33 (including) | r33 (including) |
| Nginx_plus | F5 | r33-p1 (including) | r33-p1 (including) |
| Nginx_plus | F5 | r33-p2 (including) | r33-p2 (including) |
| Nginx_plus | F5 | r33-p3 (including) | r33-p3 (including) |
| Nginx_plus | F5 | r34 (including) | r34 (including) |
| Nginx_plus | F5 | r34-p1 (including) | r34-p1 (including) |
| Nginx_plus | F5 | r34-p2 (including) | r34-p2 (including) |
| Nginx_plus | F5 | r35 (including) | r35 (including) |
| Nginx_plus | F5 | r35-p1 (including) | r35-p1 (including) |
| Nginx_plus | F5 | r36 (including) | r36 (including) |
| Nginx_plus | F5 | r36-p1 (including) | r36-p1 (including) |
| Nginx_plus | F5 | r36-p2 (including) | r36-p2 (including) |
| Red Hat Enterprise Linux 10 | RedHat | nginx-2:1.26.3-2.el10_1.1 | * |
| Red Hat Enterprise Linux 10.0 Extended Update Support | RedHat | nginx-2:1.26.3-1.el10_0.8 | * |
| Red Hat Enterprise Linux 8 | RedHat | nginx:1.24-8100020260401080144.489197e6 | * |
| Red Hat Enterprise Linux 9 | RedHat | nginx:1.24-9070020260331134728.9 | * |
| Red Hat Enterprise Linux 9 | RedHat | nginx-2:1.20.1-24.el9_7.2 | * |
| Red Hat Enterprise Linux 9 | RedHat | nginx:1.26-9070020260407080353.9 | * |
| Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions | RedHat | nginx-1:1.20.1-10.el9_0.3 | * |
| Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | RedHat | nginx-1:1.20.1-14.el9_2.5 | * |
| Red Hat Enterprise Linux 9.4 Extended Update Support | RedHat | nginx-1:1.20.1-16.el9_4.5 | * |
| Red Hat Enterprise Linux 9.4 Extended Update Support | RedHat | nginx:1.24-9040020260504195322.9 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | nginx-2:1.20.1-22.el9_6.5 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | nginx:1.24-9060020260504194843.9 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | nginx:1.26-9060020260504154614.9 | * |
| Red Hat Hardened Images | RedHat | nginx-main-1.30.0-1.hum1 | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/cds-rhel9:1776868774 | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/rhua-rhel9:1776868842 | * |
| Nginx | Ubuntu | esm-infra-legacy/trusty | * |
| Nginx | Ubuntu | esm-infra-legacy/xenial | * |
| Nginx | Ubuntu | esm-infra/bionic | * |
| Nginx | Ubuntu | esm-infra/focal | * |
| Nginx | Ubuntu | esm-infra/xenial | * |
| Nginx | Ubuntu | jammy | * |
| Nginx | Ubuntu | noble | * |
| Nginx | Ubuntu | questing | * |
| Nginx | Ubuntu | upstream | * |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].