NGINX 1.31.9 fixes critical HTTP/2 RCE; unpatched Linux kernel SCTP flaw enables container escape to root
Five critical NGINX vulnerabilities allow unauthenticated remote code execution via HTTP/2, and a chainable Linux kernel SCTP privilege escalation introduced in kernel 4.15 permits full host compromise including Docker container escapes.
Summary
Security firm Xint has disclosed five critical vulnerabilities in the NGINX web server, with the most severe enabling unauthenticated remote code execution on servers with HTTP/2 enabled. The company also identified a local privilege escalation vulnerability in the Linux kernel's Stream Control Transmission Protocol (SCTP) subsystem, present since kernel 4.15, which can be chained with the NGINX flaw to achieve root access on the host system. Xint demonstrated a complete container escape, obtaining a root shell on the host from within a Docker container running NGINX. The SCTP module is installed by default on many Linux distributions and auto-loads when any program opens an SCTP socket, making the attack surface widely exposed where network reachability exists.
NGINX 1.31.9 has been released to address the web server vulnerabilities. However, no kernel patch is yet available for the SCTP privilege escalation. Xint advises immediate upgrade to the fixed NGINX version and recommends blocking the SCTP kernel module on systems that do not require it as an interim mitigation until a kernel fix ships.
Vulnerability chain and kernel attack surface
- NGINX HTTP/2 RCE: The most severe of five disclosed vulnerabilities permits unauthenticated remote command execution specifically when HTTP/2 is enabled on the affected nginx server.
- Kernel SCTP LPE (4.15+): A local privilege escalation exists in the Stream Control Transmission Protocol subsystem, introduced in Linux kernel 4.15, with no patch currently available from upstream.
- Container escape demonstrated: Xint successfully obtained a root shell on the Docker host by chaining the NGINX RCE with the kernel SCTP vulnerability, bypassing container isolation boundaries.
- SCTP auto-loading behavior: The SCTP kernel module is present by default on numerous Linux distributions and loads automatically upon first socket open, expanding attack surface without explicit administrator action.
- Shared kernel risk: Because all containers on a host share a single kernel, successful exploitation of the SCTP flaw grants control over the host and every container running on it, not merely the compromised container.
Why it matters
This vulnerability chain represents a severe threat to containerized infrastructure running NGINX, as the demonstrated Docker escape undermines core isolation guarantees that Linux deployments rely upon. System administrators and distribution maintainers face immediate pressure to deploy NGINX 1.31.9 while awaiting a kernel patch, and the default presence of SCTP on major distributions means many hosts are exposed without administrators' awareness. Cloud providers and DevOps teams running container orchestration platforms should prioritize SCTP module blacklisting where the protocol is unnecessary.
What to do
- Update NGINX to version 1.31.9.
- Block the SCTP kernel module on hosts that do not require it.
Original reference: lwn.net →