GEEK HAUS

Summary and commentary: Geek Haus. Editorial responsibility: Jay Jang, CEO

Back to feed

Cloudflare says its HTTP proxy shields nginx origins from three of five nginx2root flaws, but urges patching

·Cloudflare Blog
read original ↗
Cloudflare says its HTTP proxy shields nginx origins from three of five nginx2root flaws, but urges patching

Geek Haus editorial team · Sources and editorial policy

EDITOR BRIEF

F5 and nginx.org disclosed five nginx memory-corruption vulnerabilities; the most broadly applicable affects HTTP/2-enabled servers, while others require HTTP/3, resolver, or mail-proxy configurations. Cloudflare says its edge is patched and its HTTP proxy blocks the attack traffic for three flaws, but resolver and mail-proxy cases are not fully protected; it recommends upgrading to nginx 1.30.7 or 1.31.9, or a vendor-fixed build.

COMMENTARY

For origins reachable only through Cloudflare’s HTTP proxy, terminating HTTP/2 and HTTP/3 at the edge prevents the crafted client frames needed for three attacks from reaching nginx, buying time to patch. That protection does not cover direct origin access, mail proxy traffic, or all resolver configurations, so teams should verify exposure and update; the article also notes that no kernel fix was available for the separate Linux privilege-escalation bug.

COMMENTS

Discussion

> geekhaus:~$ read next

Related articles