I see some irony here. For a period of time, Google chose not to include JPEG XL in Chrome because vulnerabilities in the library could compromise the software - a legitimate concern. Yet, Google is the author of the Brotli data compression format a decade before the JPEG XL drama, and was happy to use it in Chrome and let others use the library, despite the fact that it also increases the attack surface.
Well, whoever picked the name HTTP2Shell certainly didn't use any intelligence, artificial or genuine.
It's so meaningless, broad and undescriptive of the actual issue. No it probably doesn't affect an HTTP server with nothing else behind it, so why is HTTP being blasted?
I think we've all seen where an LLM names a session, issue, or PR based on its early understanding and fails update it later.
AI isn't being asked to review the title, and it doesn't have experience or think, so of course it's not going to flag it.
No human reviews anything anymore so of course they aren't going to catch it.
Edit: AI for as good as it is at "writing" is terrible at writing and particularly at naming things. I had an AI name a client OpenAICompatibleEmbeddingClient. "Brooooo.. I think "compatible" is implied, who names stuff like that?!"
Yeah, because the six number chunk is near the limit of recall. Don't remember CVE-2026 since the year and CVE can be reconstructed from time memory. You know it came up this year. Remember that vuln 111-497 (as two chunks) came out this year, and remembering two short chunks is easier.
You and I, my friend, are the only ones in this thread not being sent to work in the glitter mines of south Arkansas as enemies of God's Country. SI has the best names, other intelligence is vastly inferior, using it is worse than many schisms of -isms combined.
Much prefer the Broccoli2Shell name & site (for the same vuln): https://broccoli2shell.com/. For starters, I'm pretty sure you can hit this without HTTP if you do any manual Brotli decoding, HTTP just happens to be the most common case that comes up.
1. See a vuln domain reported, clone the site.
2. Wait for it to expire and snag it.
3. Republish the site with malware
4. Watch people dither about domain names and stuff instead of taking time to fix things.
GitHub.io domains, workers.dev domains, etc are all free domains.
Clever use and abuse of some startups can get you a free domain with a signup package that you can subsequently transfer out, but those are harder to find these days.
Seriously, the bad guys figure this out all the time.
No, they aren't. The website doesn't list an author, so fame is out of the question, and they say exactly how severe the bug is rated ("Rated 9.2 Critical (CVSS 4.0) by GitHub, High by Node.js.") right at the top.
There is named entity in the end, and "we" statement. But yeah, I was speaking in general, not so specifically about this page. It is better than most who do this.
nayuki just now
netsharc 18 hours ago
It's so meaningless, broad and undescriptive of the actual issue. No it probably doesn't affect an HTTP server with nothing else behind it, so why is HTTP being blasted?
You might as well call it Exploit Pro Max...
Rapzid 15 hours ago
AI isn't being asked to review the title, and it doesn't have experience or think, so of course it's not going to flag it.
No human reviews anything anymore so of course they aren't going to catch it.
Edit: AI for as good as it is at "writing" is terrible at writing and particularly at naming things. I had an AI name a client OpenAICompatibleEmbeddingClient. "Brooooo.. I think "compatible" is implied, who names stuff like that?!"
rafram 9 hours ago
Rapzid 3 hours ago
Which they will happily do if you ask them "why" they did something. 100% they will give their best "well actually" impression.
rmaxdev 11 hours ago
PalmPilotProMax 5 hours ago
lifeisloving 9 hours ago
super256 5 hours ago
(Actually you eat cake and drink coffee on a funeral, but it's still called like that in some parts of Austria.)
CharlieDigital 18 hours ago
cromka 6 hours ago
rererereferred 14 hours ago
kevincox 6 hours ago
ygjb 5 hours ago
N19PEDL2 14 hours ago
cowlevel 15 hours ago
croes 15 hours ago
techpression 17 hours ago
CharlieDigital 17 hours ago
photios 16 hours ago
anilakar 16 hours ago
devsda 15 hours ago
reddozen 17 hours ago
Stitch4223 4 hours ago
TZubiri 13 hours ago
Now, whether it's warranted or not, that's another matter, but they know how to appeal for maximum awareness/interaction.
groundzeros2015 15 hours ago
sigmarule 14 hours ago
pimterry 16 hours ago
illusive4080 13 hours ago
sbarre 11 hours ago
reassess_blind 10 hours ago
mynameisvlad 10 hours ago
ygjb 5 hours ago
1. See a vuln domain reported, clone the site. 2. Wait for it to expire and snag it. 3. Republish the site with malware 4. Watch people dither about domain names and stuff instead of taking time to fix things.
ygjb 5 hours ago
GitHub.io domains, workers.dev domains, etc are all free domains.
Clever use and abuse of some startups can get you a free domain with a signup package that you can subsequently transfer out, but those are harder to find these days.
Seriously, the bad guys figure this out all the time.
cubefox 12 hours ago
nicce 10 hours ago
mynameisvlad 10 hours ago
nicce 9 hours ago
cubefox 8 hours ago
nicce 8 hours ago