Hacker news

  • Top
  • New
  • Past
  • Ask
  • Show
  • Jobs

Unauthenticated remote code execution in Nginx (https://www.wiz.io)

1492 points by speedping 1 day ago | 639 comments | View on ycombinator

black3r 1 day ago |

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.

fduran 1 day ago |

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

malikNF 1 day ago |

Hey so, does anyone know of a good tutorial on getting in to woodwork?

fn-mote 1 day ago |

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.

pelzatessa 1 day ago |

If you want to check if your host might be vulnerable:

https://xint.io/blog/nginx2root-remote-code-execution#23-com...

Workarounds if you're vulnerable and can't update immediately:

https://xint.io/blog/nginx2root-remote-code-execution#33-eme...

yerimyerimie 1 day ago |

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/

testtestmetest 1 day ago |

You need 128Gb of http/2 traffic and specific cpu instructions to get this to work.

https://x.com/Laughing_Mantis/status/2123146699396858260

Its a non issue, but people just want to be told AI is God or something and the world is ending.

Its a non issue.

hackthemack 1 day ago |

I notice a phenomena that when older software has a critical vulnerability, like say Apache, you get quite a few comments of "Why does anyone use that? Use Nginx"

But when newer software has the same vulnerability, you do not see the same kind of comments.

There always seems to be a latent stance in IT that newer is better.

aftbit 1 day ago |

Hardly anyone talking about the Linux SCTP bug that they used to LPE out of the container. Apparently that's a zero-day without a public CVE number yet? Presumably they're coordinating with the kernel team and distros to get it patched first. Of course, one might just assume that there are a bazillion LPEs available to even a properly confined rootless container, but ... yuck.

nikcub 1 day ago |

every major exploit now comes with a marketing website - nginx2root dot com in this case

the certificate for it was issued on the 2nd of November

if you were scanning CT logs you would have had a 16 day head start on RE'ing this

there are more examples in the current CT logs

https://api.certspotter.com/v1/issuances?domain=nginx2root.c...

ROllerozxa 1 day ago |

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

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

codedokode 1 day ago |

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.

Retr0id 1 day ago |

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

Is this some kind of record for bug collision?

8by3 1 day ago |

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

Buttons840 1 day ago |

Everyone's worried about security right now, even non-tech people, but hasn't half the nation's personal data been leaked twice a month for the last decade or two?

I know times are changing, it's just curious that nobody seemed to care until now.

TuckerBMorgan 1 day ago |

I wonder when all of this die down. I assume at some tipping point most software will be written/patched with LLMs and so hopefully (fingers crossed) more resistent to these bugs.

Certainly a stressful time for sysadmins everywhere, let us hope your coworkers are picking up your beer tab

hosteur 1 day ago |

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

userbinator 1 day ago |

HTTP/2 again, not surprisingly. The curse of complexity strikes again. When I first saw the spec, I knew it would be far more difficult to implement correctly than 1.1 or 1.0. While 1.x is not ideal either (parsing a protocol that involves free-form text with no fixed limits is always a bit scary), at least it has a much smaller attack surface.

On the bright side, perhaps "security review" of code which involves throwing it at an AI and fixing what it finds before releasing will become a normal practice.

"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies." - C.A.R. Hoare

Juvination 1 day 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.

brisky 1 day ago |

Reading news like this makes me remember the ship hacking scene from GITS Innocence. In the end there will be AI attacking vs AI defending. Humans will be too slow to participate. Defender AIs should be coming soon - maybe some sort of proactive memory and usage anomaly pattern monitoring AI systems?

puszczyk 1 day ago |

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

npteljes about 23 hours ago |

With the amount and speed of random vulns cropping up, reducing the attack surface rings more true than ever.

Thinking about my home server where I host some stuff for household use, I think moving to VPN + local access only will be my new strat. So now the random webservers won't be exposed to the internet, only whatever I will use for VPN.

tgma 1 day ago |

As much as everyone is getting allergic to Rust migrations that sometimes make little sense, keeping network-facing daemons in C is just asking for it at this point. It's time to start seriously migrating to web servers like ferron.sh or https://xinproxy.com or whatnot.

tancop 1 day 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.

undefined 1 day ago |

undefined

brocklobsta 1 day ago |

Running a homelab is quickly turning into a bigger and bigger liability. Just disabled http/2 on my cluster.

andrelaszlo 1 day ago |

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

jawiggins 1 day ago |

Is this the reason why those banks were down the other day? Did they get advanced knowledge so they could patch their instances? Kind of questionable that the AI labs are creating a two-tiered system for system security if so.

jascha_eng 1 day ago |

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

pelzatessa 1 day ago |

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

hacker_homie 1 day 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.

downsplat about 22 hours ago |

If anyone needs it, the Ubuntu package is up: https://ubuntu.com/security/CVE-2026-123633

BSTRhino 1 day ago |

I saw this and realised I'm running nginx in a docker container, very easy update, no waiting for the distro to make the update available

ppjim 1 day ago |

leca 1 day ago |

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

undefined 1 day ago |

undefined

xr8 1 day ago |

Ops is not fun these days … used to pinned versions and an auditing approval process with SecDevOps … how are you mostly automate the process in a you build it you run it environment ?

thunfischtoast 1 day ago |

Is there a summary in a nutshell? The Wiz article just repeats the same sentences over and over again

xyproto 1 day ago |

Most web servers are undergoing a security tsunami right now. It's important to switch to the ones that are on the fixed side of the tsunami, IMO.

undefined 1 day ago |

undefined

hokkos 1 day 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...

george_max 1 day ago |

FYI, you need to send around 128GB of data for this bug to work, so not exactly discreet or quick.

beaviskhan 1 day ago |

If you use Cloudflare to proxy traffic, you can disable HTTP/2 quickly and easily: https://developers.cloudflare.com/speed/optimization/protoco...

iqbal1980 1 day ago |

Thank you! I had to patch bunch of products I'm working on.

manishrana 1 day ago |

Everyday we are seeing new vulnerabilities. Thanks to AI

sarreph 1 day ago |

I wonder how much of this exploitation will push the industry towards closed-source. Previously the advantage of OSS was trust and collaborative improvement, but that is getting eroded quite heavily now by the barrage of attacks and insidious discovery.

The first step was closing contributions down to known contributors and maintainers. Maybe there’ll be a similar step where only a select group will be able to access — and attest to — the code?

Almost like “Restricted Access Source” or “Withheld Source”

levkk 1 day ago |

Pretty funny times. AI is making it faster to both write insecure code and to detect buffer overflows. Sell both the problem and the solution. Genius.

It'll take a few years for the market to adjust. If nothing else, businesses are good at figuring out ROIs, eventually.

wasmitnetzen 1 day ago |

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

Cue xkcd

undefined 1 day ago |

undefined

therepanic 1 day ago |

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

unsloppable 1 day ago |

Is it time to vibe code my whole stack so I'm secure through obscurity?

Only half joking.

nojs 1 day ago |

"Check if our site is vulnerable to the latest nginx security advisory"

> Error: API Error: Opus 5.5's safeguards flagged this session

Literally the first message, lol.

philipwhiuk 1 day ago |

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

otagekki 1 day ago |

What a beautiful way to start the morning, after PHP2Shell last month and now this!

dirkc 1 day ago |

Just what I needed on a Wednesday evening after promising myself I'll go to bed before 10. Oh well, thanks for the disclosure.

artooro 1 day ago |

Thankfully this time there are patches available right away, unlike that PHP bug not too long ago!

undefined 1 day ago |

undefined

K0nserv 1 day 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.

fvrshaibu 1 day ago |

its crazy how exploits are being discovered in software nowadays, especially using AI

iqbal1980 1 day ago |

Was this discovered using an AI?

sourcecodeplz 1 day ago |

the new "hack" now is to monitor wide-spread repos for critical PRs

j45 1 day ago |

My firewall needs a firewall

sebiw 1 day 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.

FLeXMurphy 1 day 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?

gsich about 24 hours ago |

Overhyped

johnbellone 1 day ago |

The beatings will continue until morale improves.

dmonterocrespo 1 day ago |

Critical open source software will have to be shut down to the public

perrygeo 1 day ago |

I was talking with someone about buffer overflows due to HTTP requests this morning. I think I said something like "but we don't need to worry about that, just put nginx in front of it." Sigh. Off to update some VMs. Again.

ronfriedhaber 1 day ago |

Great work by wiz.

Culonavirus 1 day ago |

> Complexity can no longer be relied upon as a barrier to discovery or exploitation.

I mean sure if we close our eyes and ears we can ignore the elephant in the room that is proprietary, closed source software.

AtNightWeCode 1 day ago |

Maybe you should not run in production a Russian reverse proxy slash web server commercialized by F5 written in C to begin with...

brynet 1 day ago |

Nginx used to be in the OpenBSD base system between 2012-2015.

12 years on, OpenBSD's port of nginx still maintains its default chroot(2) patch.

https://raw.githubusercontent.com/rnagy/nginx_chroot_patch/m...

I recommend reading Reyk Flöter's AsianBSDcon 2015 paper about nginx and the thing that replaced it in base.

https://www.openbsd.org/papers/httpd-asiabsdcon2015.pdf

1vuio0pswjnm7 1 day ago |

"Both vulnerabilities are memory-safety issues in how NGINX handles HTTP/2 traffic."

HTTP/2 again. First Apache, now NGINX

I rarely use HTTP/2, I rarely use a popular web browser, I use a TLS forward proxy that has HTTP/2 support but I prefer HTTP/1.1

I find that 1.1 is faster for the way I use the www (text-only, no images, CSS, Javascript, cookies, advertising, tracking), plus the 1.1 protocol comes from academia not Google, Akamai, etc.

TZubiri 1 day 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.

hollerith 1 day ago |

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

superkuh 1 day ago |

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

jon128 1 day ago |

nginx is so pervasive, these CVEs are serious.

EGreg 1 day ago |

If you are running a PHP site, you don't need an external webserver anymore, like Apache, NGINX or Caddy.

This webserver is not vulnerable to PHP2Shell nor this TLS issue, because it's completely userland PHP:

https://github.com/Qbix/webserver

It's now been battle-tested in production, and also supports websockets, etc.

(However, it doesn't support sendfile, because PHP doesn't have support for that, so it's not as fast as nginx for sending static files. This shouldn't make a difference, though, if you use a CDN in front.)

Imustaskforhelp 1 day ago |

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)

charlie2agent 1 day ago |

[flagged]

yoy0721 1 day ago |

[flagged]

adilbasari 1 day ago |

[flagged]

binarybriefing about 17 hours ago |

[flagged]

Agataproximadev 1 day ago |

[flagged]

aqibkhan026 1 day ago |

[dead]

undefined 1 day ago |

undefined

FAYSAL-KA 1 day ago |

i dont know what it is this but good work

testtestmetest 1 day ago |

[flagged]

testtestmetest 1 day ago |

[flagged]

gabucino 1 day ago |

[flagged]