1492 points by speedping 1 day ago | 639 comments | View on ycombinator
black3r 1 day ago |
fduran 1 day ago |
malikNF 1 day ago |
fn-mote 1 day ago |
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 |
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 |
testtestmetest 1 day ago |
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 |
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 |
nikcub 1 day ago |
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 |
codedokode 1 day ago |
Retr0id 1 day ago |
Is this some kind of record for bug collision?
8by3 1 day ago |
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 |
I know times are changing, it's just curious that nobody seemed to care until now.
TuckerBMorgan 1 day ago |
Certainly a stressful time for sysadmins everywhere, let us hope your coworkers are picking up your beer tab
hosteur 1 day ago |
userbinator 1 day ago |
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 |
brisky 1 day ago |
puszczyk 1 day ago |
edit noted it's about a Kubernetes controller
npteljes about 23 hours ago |
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 |
tancop 1 day ago |
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 |
brocklobsta 1 day ago |
andrelaszlo 1 day ago |
jawiggins 1 day ago |
jascha_eng 1 day ago |
pelzatessa 1 day ago |
hacker_homie 1 day ago |
downsplat about 22 hours ago |
BSTRhino 1 day ago |
ppjim 1 day ago |
leca 1 day ago |
undefined 1 day ago |
xr8 1 day ago |
thunfischtoast 1 day ago |
xyproto 1 day ago |
undefined 1 day ago |
hokkos 1 day ago |
george_max 1 day ago |
beaviskhan 1 day ago |
iqbal1980 1 day ago |
manishrana 1 day ago |
sarreph 1 day ago |
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 |
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 |
Cue xkcd
undefined 1 day ago |
therepanic 1 day ago |
unsloppable 1 day ago |
Only half joking.
nojs 1 day ago |
> Error: API Error: Opus 5.5's safeguards flagged this session
Literally the first message, lol.
philipwhiuk 1 day ago |
otagekki 1 day ago |
dirkc 1 day ago |
artooro 1 day ago |
undefined 1 day ago |
K0nserv 1 day ago |
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 |
iqbal1980 1 day ago |
sourcecodeplz 1 day ago |
j45 1 day ago |
sebiw 1 day ago |
Edit: All good. They released the new versions within 30 mins.
FLeXMurphy 1 day ago |
gsich about 24 hours ago |
johnbellone 1 day ago |
dmonterocrespo 1 day ago |
perrygeo 1 day ago |
ronfriedhaber 1 day ago |
Culonavirus 1 day ago |
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 |
karel-3d 1 day ago |
https://security-tracker.debian.org/tracker/CVE-2026-123007
Debian still vulnerable in all versions.
brynet 1 day ago |
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.
1vuio0pswjnm7 1 day ago |
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 |
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 |
superkuh 1 day ago |
jon128 1 day ago |
EGreg 1 day ago |
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 |
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 |
yoy0721 1 day ago |
adilbasari 1 day ago |
binarybriefing about 17 hours ago |
Agataproximadev 1 day ago |
aqibkhan026 1 day ago |
undefined 1 day ago |
FAYSAL-KA 1 day ago |
testtestmetest 1 day ago |
testtestmetest 1 day ago |
gabucino 1 day ago |
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.