When NGINX Plus or NGINX OSS are configured to use the HTTP/3 QUIC module and the network infrastructure supports a Maximum Transmission Unit (MTU) of 4096 or greater without fragmentation, undisclosed QUIC packets can cause NGINX worker processes to leak previously freed memory.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Nginx_open_source | F5 | 1.25.0 (including) | 1.26.1 (excluding) |
| Nginx_plus | F5 | r30 (including) | r30 (including) |
| Nginx_plus | F5 | r30-p1 (including) | r30-p1 (including) |
| Nginx_plus | F5 | r30-p2 (including) | r30-p2 (including) |
| Nginx_plus | F5 | r31 (including) | r31 (including) |
| Nginx_plus | F5 | r31-p1 (including) | r31-p1 (including) |