Re:Pre-auth RCE in Nginx HTTP/2 handling
by quesera on Wednesday November 18, 2026 @02:32PM
(#50550945)
Someone registered ping2shell.com on Nov 9th, nine days ago.
ping2root.com is available though. :)
Re:Pre-auth RCE in Nginx HTTP/2 handling
by badgersnake on Wednesday November 18, 2026 @02:39PM
(#50551051)
And irresponsible disclosure but a bunch of attention seeking tossers
Re:Pre-auth RCE in Nginx HTTP/2 handling
by pixl97 on Wednesday November 18, 2026 @05:38PM
(#50553327)
Sitting on flaws is dead, the responsible disclosure people can get lost. AI finds and exploits flaws in hours. We also have little knowledge if the people finding the exploits have already intentionally or unintentionally leaked said exploits to AI providers.
If you want to promote responsible anything, go for responsible writing of software in the first place.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by frangonf on Wednesday November 18, 2026 @04:01PM
(#50552080)
Security companies should buy all this $tech2root domains as a diverting measure first and also as a pretty safe investment, given current trends.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by nikcub on Wednesday November 18, 2026 @05:03PM
(#50552852)
there's one that squatted on 30+ domains a few weeks ago that i saw
Re:Pre-auth RCE in Nginx HTTP/2 handling
by aftbit on Wednesday November 18, 2026 @05:40PM
(#50553367)
but what about $tech4shell.com tho?
Re:Pre-auth RCE in Nginx HTTP/2 handling
by AtNightWeCode on Wednesday November 18, 2026 @07:53PM
(#50554605)
I scan new domain names but for a different reason. There is an insane amount of nonsense domains registered everyday. Would be hard to tell just based on that.
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...