logoalt Hacker News

Pre-auth RCE in Nginx HTTP/2 handling

457 points • by speedping • today at 3:19 PM • 158 comments • view on HN

Comments

black3r • today at 4:43 PM

The bug was apparently fixed in open source repo a week earlier, this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week (the commit message even included "Reported by Xint.io" and I'm guessing skilled black hats would know about Xint)

Given that in this case the workaround is as simple as disabling http2, there is honestly no reason why F5/Nginx or any of the reporting teams couldn't at least put out a PSA to disable http2 for the time being before basically telling the whole wide world this exists and how to exploit it.

Especially for software like Nginx which powers a huge part of the internet.

➕ show 7 replies
fduran • today at 6:40 PM

Small consolation but HTTP/2 is not enabled by default in Nginx and "only" 12% of servers run it (still huge at Internet scale) https://w3techs.com/technologies/segmentation/ce-http2/web_s...

➕ show 1 reply
fn-mote • today at 4:20 PM

AI is burning down the internet. This is insane.

Are we going to discover in a year that every server online this month had a rootkit installed? There’s got to be thousands who are too small time to wipe and reinstall.

➕ show 12 replies
ROllerozxa • today at 3:49 PM

Well I guess this was the vuln that was teased about on Mastodon some hours ago:

https://is-a.cat/@ar/117634569518544368

8by3 • today at 4:38 PM

FreeBSD is unpatched,

I got worried for a sec, then remembered all my nginx lives behind HaProxy and it looks like nginx is only vulnerable if its going http2/TLS directly.

Now I sit and wait for an HaProxy announcement...

ps. if you are on FreeBSD and doing TLS directly

sed -i.bak -E 's/^([[:space:]]server[[:space:]]\{)$/\1\ http2 off;/' /usr/local/etc/nginx/nginx.conf ;service nginx restart

➕ show 2 replies
codedokode • today at 4:46 PM

Integer underflow again. Programming languages should trap on integer overflows and not ignore them. Don't care about legacy CPUs not having a trap for this - they will go sooner or later.

➕ show 2 replies
yerimyerimie • today at 3:58 PM

Fun collision! We (Xint) were one of the teams and actually ended up finding a few more bugs along the way. If anyone wants to check it out our writeup covers those plus the full chain to root: https://nginx2root.com/

➕ show 3 replies
Retr0id • today at 3:42 PM

> Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered

Is this some kind of record for bug collision?

➕ show 5 replies
puszczyk • today at 5:51 PM

ugh, looks like if you still run ingress-nginx controller (you shouldn't but it was super popular in Kubernetes docs/community and there was a very little time to migrate away) you won't get these patches https://github.com/kubernetes/ingress-NGINX

edit noted it's about a Kubernetes controller

hosteur • today at 3:49 PM

So work around is to disable http/2 and only allow http/1.1?

➕ show 3 replies
pelzatessa • today at 6:03 PM

OPs article mentions 2 CVEs, however this one claims that there are 5 new ones: https://news.ycombinator.com/item?id=50547423

manishrana • today at 6:28 PM

Everyday we are seeing new vulnerabilities. Thanks to AI

hacker_homie • today at 5:50 PM

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.

➕ show 1 reply
Juvination • today at 4:56 PM

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.

➕ show 1 reply
tancop • today at 4:45 PM

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.

➕ show 3 replies
jascha_eng • today at 4:03 PM

Never turned http2 on in my side project pfew. But still, this is one is pretty rough...

➕ show 1 reply
andrelaszlo • today at 5:52 PM

I assume OpenResty is affected as well? ("High Performance Web Platform Based on Nginx and LuaJIT")

hokkos • today at 5:15 PM

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...

testtestmetest • today at 6:44 PM

To all the people here that would like to give AI credit for everything, and dont think it matters that everyone at Wiz is Israel Ex Cyber "Defense", and all you need is AI to find things like this. I have a challenge for you:

If you think you can do it or that anyone with AI dan be dangerous. Please, right now put everything down.. Go make a h1,bugcrowd acct and start making millions. If its as easy as having access to llms please go get rich. I assure you just having access to tokens doesnt get you very far.

TZubiri • today at 6:31 PM

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.

FLeXMurphy • today at 6:29 PM

Is this going to end up being another exploit that requires a ridiculous amounts of special conditions so as to not actually be applicable to majority of sites running nginx?

wasmitnetzen • today at 4:21 PM

Docker images are a bit delayed because of unstable GitHub runners: https://github.com/nginx/docker-nginx/pull/1075#issuecomment...

Cue xkcd

therepanic • today at 4:57 PM

What’s the point of these researchers if their autonomous system is now finding these vulnerabilities?

➕ show 1 reply
testtestmetest • today at 6:21 PM

Isreael btw everyone at Wiz is a veteran of Unit 8200.

But sure, keep telling yourself this is AI lmfao and anyone can hack because of LLMs.

philipwhiuk • today at 4:13 PM

So...what library/tool/language is next folks? Presumably Wiz is sitting on a bunch more.

leca • today at 3:31 PM

How many hours before this is exploited in the wild ? Probably not all that long, that blog has a significant amount of details.

➕ show 1 reply
K0nserv • today at 3:50 PM

Just another set of unfortunate examples of programmers who are bad at C, definitely not a C problem.

EDIT: Okay, this comment was snarky and not in good spirit. To be serious, I think we are increasingly seeing that the notion that humans can write non-trivial amounts of C correctly is false. Especially in the face of AI-assisted vulnearbility hunting these programs a crumbling. This is not an indictment of humans, it's a sign that C is not equipped to meet this moment.

➕ show 3 replies
sebiw • today at 3:35 PM

Uhm, am I missing something or are the patched releases not out yet? Why disclose this level of detail when the patches are not ready yet?

Edit: All good. They released the new versions within 30 mins.

➕ show 7 replies
ronfriedhaber • today at 4:02 PM

Great work by wiz.

superkuh • today at 3:34 PM

It seems like it always HTTP/2 (except when it's regex) with nginx. Glad I'm http/1.1 only.

➕ show 1 reply
johnbellone • today at 3:38 PM

The beatings will continue until morale improves.

➕ show 2 replies
FAYSAL-KA • today at 5:37 PM

i dont know what it is this but good work

hollerith • today at 4:48 PM

HTTP/2 is so complicated that the code that handles it tends to be vulnerable. What a surprise

➕ show 2 replies
Imustaskforhelp • today at 4:46 PM

Okay now I believe that AI is finally burning down the internet and that all the incidents are not just pure coincidences.

Some of these things could've been coincidence but I remember seeing an apache RCE a few days back and people said, oh imagine using Apache, I use Nginx and now not a few days later Nginx has RCE.

And this is just a very very small iceberg of all the recent RCE cases with a serious uptick that I have just observed on Hackernews alone.

Basically, there is a sort of justification that people provide with one RCE is that that software X has had issues and to use Y software, but now that X,Y software and A1...Z1 all are being found to have quite severe bugs. I can't in good faith just consider it to be a coincidence.

Though I do still hope that this might just be a coincidence and not a recurring pattern, because, A) I don't wish to live in that reality where each software that we trusted seems to have quite so many bugs and which would be exploited and B) Have it be continued for a prolonged period of time.

Though the plus point is that we are gonna find extremely resilient software after all of this hopefully as sort of a need in our times.

We might have to agree that the cybersecurity world seems to have changed (though I am no expert right now to comment on it but I am curious what experts think)

➕ show 2 replies
Agataproximadev • today at 5:46 PM

[flagged]

gabucino • today at 4:35 PM

[dead]