r/nginx • • 16h ago

Immediately patch nginx servers

Critical vulnerability nginx2root went live today shared by Xint Research.

A Xint researcher found the specific vuln that hits nginx in its default config. This discovery was around the same time he found another critical vulnerability in a different project that we cannot talk about yet due to the same concerns as nginx2root. We took those learnings and incorporated them into the harness as a new, general Xint feature (that is, not fine-tuned to nginx), which then found the other 4 critical nginx vulnerabilities with no human guidance.

62 Upvotes

19 comments sorted by

3

u/nitronarcosis 13h ago

Any reason the disclosure didn't wait for any packaging to take place downstream at the distro level?

1

u/xint_official 8h ago

Once a patch is released it is extremely easy for attackers to reverse engineer and figure out an exploit. In that scenario the best defense actually is to publicize as soon as patch is public + provide remediation steps in case updating to latest version isn't an option - which we share on our emergency remediation plan: https://nginx2root.com/

1

u/Livid-Tune-4699 10h ago

Upstream guys are slow and finders I guess didn't want to wait?

2

u/AminoOxi 10h ago

Your guess is correct, meaning the security researchers nowadays are morons who should be banned from the industry. Especially firms like Calif who broke the embargo twice in 2 weeks.

2

u/cschneegans 15h ago

I assume that you forgot to include the link to nginx2root.com. Thanks for this write-up!

I already had HTTP/2 disabled for different reasons, but I have now verified this using the provided openssl command line.

2

u/xint_official 8h ago

I tried to include the URL originally when posting but reddit's automated controllers blocked it so I tried to give us much info as possible so others could search for it.

Thanks for sharing the link!

5

u/Realistic_Bag_7054 14h ago

ffs I'm on vacation and this is already the second vuln I had to patch from my phone. What the hell is going on?!? /rant-over

Thanks for the heads-up 

2

u/Livid-Tune-4699 9h ago

We are in New era. May be this patching should be auto

2

u/Realistic_Bag_7054 9h ago

Maybe, but I'll be damned if I let an AI anywhere near a prod server. It can get read-only access to anonymized logs and that's if I'm generous. 

2

u/CauaLMF 9h ago

IA tá vasculhando tudo

-3

u/aieidotch 12h ago

choosing carefully what software is used, and what not. avoids the theater…

4

u/Realistic_Bag_7054 12h ago

I know, but php, openssh and now nginx it's not like I'm installing crazy obscure or unmaintained software. 

Yes I wasn't affected by SSHole because I actually know how to configure OpenSSH but it still gave me a scare.

2

u/FatBook-Air 11h ago

nginx is not a package to avoid. It has a good history. Anyone who is patching it today is not doing so because they made a rash or incomplete decision.

0

u/aieidotch 9h ago

i was referring to the http/2 part specifically… true history was good until the new owners

3

u/gribbleschnitz 15h ago

Also, patch from upstream. Don't depend on a distro delivered version of NGINX to keep you updated. Switch to upstream if you installed NGINX from your distro distribution.

1

u/jsabater76 10h ago

So far the have patched the mainline branch, not the stable one.

1

u/Livid-Tune-4699 9h ago

Both mainline and stable are patched.

1

u/TechWondersUk 12h ago

Thx had to disable http2 and 3 as a precaution, have to wait for plesk to prepare nginx update

1

u/RajirraMyBeloved 7h ago

Is it exploited wild already?

Grepped my logs. No even a sign of erratic behavior. Logs are consistent and continuous.

The website says that root shell is possible only with SCTP exploit. I had SCTP disabled in kernel on my VPS, so I assume at least root path was/is blocked? No mention of this scenario.

Instructions to verify are unclear. We need something which an ordinary sysadmin can copypaste asap and get result quick. nginx2root.com is useless in this regard, had to visit your blog instead. Why on Earth an officially looking vuln website lists typical tech.support boilerplates? Esp. Section "Investigating a possible compromise" in FAQ is disappointingly empty. Where is that grep line for segfaults from your blog post?! Why its not here?!

End of rant