Top
Best
New

Posted by speedping 3 hours ago

Pre-auth RCE in Nginx HTTP/2 handling(www.wiz.io)
465 points | 161 commentspage 3
testtestmetest 18 minutes ago|
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 31 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.

FLeXMurphy 33 minutes ago||
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 2 hours ago||
Docker images are a bit delayed because of unstable GitHub runners: https://github.com/nginx/docker-nginx/pull/1075#issuecomment...

Cue xkcd

therepanic 2 hours ago||
What’s the point of these researchers if their autonomous system is now finding these vulnerabilities?
pixl97 1 hour ago|
Making sure AI isn't hallucinating.
philipwhiuk 2 hours ago||
So...what library/tool/language is next folks? Presumably Wiz is sitting on a bunch more.
K0nserv 3 hours ago||
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.

marvinborner 2 hours ago||
The patch (or, one of them) seems very much like a bug that can happen independently of the programming language

https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

K0nserv 2 hours ago||
This fixes the integer underflow for CVE-2026-123007, and it's true that the underflow can happen in any language, notwithstanding whether it's UB or not. The issue is what happens as a consequence of this underflow, in this case: out of bounds copy, which is specific to C.
nh2 2 hours ago||
Some languages make it significantly easier than C to just forbid integer overflow/underflow entirely.

Given that on modern CPUs, cycles are quite fast, and memory latency is quite high, always-checked integer operations sound like an extremely good idea.

K0nserv 1 hour ago||
Sure, I usually use `overflow-checks = true` in Rust for this reason. However, it is still true that the overflow is not what caused the issue here. In Rust it would've paniced on the out of bounds copy, even with `overflow-checks = false`.
danisw 2 hours ago|||
[dead]
stevefan1999 2 hours ago||
I think you forgot the /s

C is like a Winchester Model 1897, not saying that it is a bad gun, it is what we call it the good ol' Trench gun, as it ran over the war tunnels of the Great War, and it still packs a punch today, but it only has a half-cock for some level of safety, and there is no trigger disconnector either, so you can easily slam fire it. So it is way too easy to shoot yourself in the foot.

Nowadays we like going for a AKM/AK74, for something maybe more complicated but far more reliable at the same time. That's why we want Rust.

K0nserv 1 hour ago||
I didn't think the /s was necessary
sebiw 3 hours ago|
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.

CER10TY 3 hours ago||
Well the fix for this seemingly already landed in the repo last week: https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

Given how common it's become to constantly scan popular repos for n-days, I expect someone will have already picked it up and started work on an exploit. The workaround for this (disabling HTTP/2) is also comparatively easy to what we had with PHP2Shell just a few weeks back, so I think it makes sense to release this.

ferngodfather 2 hours ago||
> Given how common it's become to constantly scan popular repos for n-days

We have people doing this on my side project and then reporting the fixed issues to try and get CVE 'credit'. Tiring.

derhuerst 3 hours ago|||
Currently, the Ubuntu [1] & Debian [2] packages seem unpatched.

[1] https://launchpad.net/ubuntu/+source/nginx [2] https://tracker.debian.org/pkg/nginx

ROllerozxa 2 hours ago||
Yeah I'm not quite sure what is going on with Debian, I would have hoped that this vulnerability would have been disclosed in collaboration with Linux distros to get a patch out?
mjhagen 3 hours ago|||
Upstream fixes are available in 1.30.7 stable and 1.31.9 mainline.
GrayShade 3 hours ago|||
They're out now.
Bender 2 hours ago|||
[dead]
More comments...