Top
Best
New

Posted by speedping 3 hours ago

Pre-auth RCE in Nginx HTTP/2 handling(www.wiz.io)
443 points | 153 commentspage 2
pelzatessa 38 minutes ago|
OPs article mentions 2 CVEs, however this one claims that there are 5 new ones: https://news.ycombinator.com/item?id=50547423
hosteur 2 hours ago||
So work around is to disable http/2 and only allow http/1.1?
Simber 2 hours ago||
Yep, that or update to 1.31.9+ or 1.30.7+ if they are available in your distro
kijin 2 hours ago||
Nobody seems to notify major distros before publishing their latest vulnerability anymore. Coordinated patches are a thing of the past, now we just hope that somebody at Red Hat and/or Canonical is reading HN today.
baggy_trough 1 hour ago||
There isn't even a mail about this on oss-security, as of now.
yread 1 hour ago|||
My Apaches still have http2 disabled from the last cve, now its njinx time
kijin 35 minutes ago||
And there were a couple of other http2 CVEs in nginx before the Apache one.

Just keep that protocol disabled for now. It's apparently too difficult for any human to write a secure implementation of http2. (As for http3, forget about it, we need AGI for that.)

dboreham 2 hours ago||
The AI gods say that http/2 is disabled in a default installation fwiw.
antiloper 2 hours ago||
Obviously... the default configuration also doesn't enable TLS, which is a de-facto prerequisite for HTTP 2. How many websites do you (or your "AI gods") think run nginx in its default configuration?
layer8 39 minutes ago||
The point is that it must have been deliberately enabled. TLS will generally be enabled out of necessity, whereas the chances for HTTP/2 are much lower, and your NGINX configuration will explicitly indicate if it’s enabled. If you don’t see “http2” in your configuration, then you know you are fine.
hacker_homie 51 minutes ago||
This sound suspiciously similar to the issue Microsoft said they were dealing with excess traffic on their front door, taking them down. maybe not an RCE but a DOS in the same http/tls code.
0xBA5ED 19 minutes ago|
Imagine there are 1 million things to know. Some of them are related but most of them aren't. Now imagine that you know 10 things.
Juvination 1 hour ago||
Nginx Proxy Manager isn't updated yet, I know a lot of people use this for their home server so just a reminder to disable http/2 here as well.
wolttam 1 hour ago|
Disabling http/2 here is a bit of a pain: you have to go through each configured host and disable it, there's no global switch
tancop 1 hour ago||
Everybody here talking about going back to HTTP/1.1, it's a good stop gap solution but we should really think about moving to HTTP3-only as fast as possible. Changing over is easy, if your server doesn't support it just put it behind a reverse proxy that does.

Unlike IPv6 it doesn't need any OS or ISP support, just a browser that's newer than 2020. Everyone outside of air gap networks and government sites should be switching.

layer8 35 minutes ago||
HTTP is used for a lot more things than web pages, and most non-browser clients in production don’t support HTTP/3. The current LTS Java version (25) for example doesn’t support it.
gkbrk 1 hour ago|||
HTTP/1.1 is still way better and way simpler than HTTP/3.
seki285 1 hour ago||
Could you please share why?
gkbrk 33 minutes ago|||
Because any HTTP spec after 1.1 is incredibly complicated. You can implement HTTP/1 in half a day, and HTTP/1.1 in a day. But HTTP/2 will probably take you a month and HTTP/3 might take something like 6 months.
lysace 38 minutes ago|||
~25 years of hardening.
SoftTalker 19 minutes ago||
Because HTTP3 was implemented without any errors? Citation needed I guess.
andrelaszlo 49 minutes ago||
I assume OpenResty is affected as well? ("High Performance Web Platform Based on Nginx and LuaJIT")
jascha_eng 2 hours ago||
Never turned http2 on in my side project pfew. But still, this is one is pretty rough...
koolba 2 hours ago|
This whole week is rough. And it’s only Wed.
jascha_eng 2 hours ago|||
well it's a good time to pitch tech debt and infrastructure cleanup. If you aren't making use of least-privilege permissions, service-mesh, netpols etc. this is the time to add all of that.

Because clearly the patching treadmill is not sustainable, you will need a a second line of defense and reduce the blast radius of every individual vulnerability.

whartung 2 hours ago|||
Actually, this is good I think.

One, as the RCEs are coming out, admins are on edge and paying more attention, so more likely to catch the annoucement on their platform. "Oh, that's on PHP, we don't use this. Oh, wait, another one?"

Two, all of these hitting at once, while they may expand the surface for attackers, it also spreads their attention. They only have so much time and bandwidth. When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

So, in the sense, it can actually slow down the actual potential impact of the revelations.

We can only hope this gives users time to get their systems up to date before they come knocking.

I mean, I know its a reach, but...who knows.

baby_souffle 2 hours ago||
> When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

Only a little bit. An attacker will just hand this to an LLM with a "ping me when this is ready to use..." prompt.

hokkos 1 hour ago||
don't know why the mainline alpine have the empty image sha-256 : https://hub.docker.com/layers/library/nginx/1.31.9-alpine/im...
TZubiri 10 minutes ago|
Hey this is TZubiri, the guy that comments that you should uninstall the dep whenever there is an post about a CVSS 9+ vuln.

Today we are going to take a look at how to avoid this vuln by not having Nginx and not using HTTP/2 (for most use cases).

We will assume that you are using Nginx for any of the following: Serving files or serving dynamic website content through some integration with a programming language.

We will be using python, but you can use any programming language that has a native integration with sockets through it's C interface (literally every language:

Step 1: import socket # import the socket library from glibc or glibc.

Step 2: socket.socket() # socket.socket()

Step 3: socket.bind((PUBLIC_ADDR,80)) # bind before listening obviously. Use a local address if you are below the IPoverty4 line.

Step 4: conn,addr = socket.accept() # this creates a connection, wrap it in a While True and a try catch for production. Sprinkle in some import threading to support multiple concurrent requests.

Step 4: req = conn.recv(4096) # split on b"\r\n\r\n" to separate headers from body, read HTTP RFCs for the rest. Feel free to reject HTTP/2 requests, they'll probably just resend as HTTP/1.1

Step 5: #Fill in the details, most likely if you are using nginx, you will end up connecting two sockets with pipe, or just storing and forwarding to another tcp endpoint. Again take a look at the HTTP RFCs and the glibc socket and stdio manuals.

Thank you for reading my tutorial, and best of lucks.

More comments...