NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_slice_module module
Summary
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_slice_module module. When the slice directive and unnamed regex captures are configured or when a background cache update happens, unauthenticated attackers can send requests that may cause uninitialized memory access in the NGINX worker process, leading to limited disclosure of memory or a restart. Impact: This vulnerability may allow remote, unauthenticated attackers to have limited control to disclose memory contents or restart the NGINX worker process. There is no control plane exposure; this is a data plane issue only. Note: The ngx_http_slice_module module is not enabled by default; it's enabled with the --with-http_slice_module configuration parameter. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
What this means
In plain English
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_slice_module module. When the slice directive and unnamed regex captures are configured or when a background cache update happens, unauthenticated attackers can send requests that may cause uninitialized memory access in the NGINX worker process, leading to limited disclosure of memory or a restart. Impact: This vulnerability may allow remote, unauthenticated attackers to have limited control to disclose memory contents or restart the NGINX worker process. There is no control plane exposure; this is a data plane issue only. The official description indicates that exploitation does not require prior authentication.
Recommended action
Primary action: update to a vendor-listed fixed release: 37.0.3.1, R36 P7, 1.31.3, 1.30.4. Vendor mitigation: When the slice directive and unnamed regex captures are configured or when a background cache update happens, unauthenticated attackers can send requests that may cause uninitialized memory access in the NGINX worker process, leading to limited disclosure of memory or a restart.
Rewritten locally from the scraped official advisory data above; no generative API is used. The vendor advisory is authoritative.
- NGINX Plus 37.0.0.1 before 37.0.3.1
- NGINX Plus R36 before R36 P7
- NGINX Plus R33
- NGINX Open Source 1.31.2 before 1.31.3
- NGINX Open Source 1.15.8 before 1.30.4
Official advisory · high-confidence parse· fetched 3 hours ago·verify at source
- 37.0.3.1
- R36 P7
- 1.31.3
- 1.30.4
Official advisory · high-confidence parse· fetched 3 hours ago·verify at source
Mitigation checklist
- When the slice directive and unnamed regex captures are configured or when a background cache update happens, unauthenticated attackers can send requests that may cause uninitialized memory access in the NGINX worker process, leading to limited disclosure of memory or a restart.
Official advisory · high-confidence parse· fetched 3 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.