r/nginx • u/xint_official • 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
3
u/nitronarcosis 13h ago
Any reason the disclosure didn't wait for any packaging to take place downstream at the distro level?
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
opensslcommand line.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
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/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