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...
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?!"
- https://lmstudio.ai/docs/developer/openai-compat
I've seen that used as a description for 2years or so.
Which they will happily do if you ask them "why" they did something. 100% they will give their best "well actually" impression.
Now, whether it's warranted or not, that's another matter, but they know how to appeal for maximum awareness/interaction.
And, most of all, is damaging to Google, which are the master of software engineering. /s
SQL Slammer didn't actually slam anything, and applied to a single vendor among many SQL providers. Heartbleed didn't make anyone's heart bleed...I mean, at least directly. Shellshock only impacted a single shell environment, again among many. Log4Shell impacted a single logging implementation, among many. Spectre and Meltdown...I mean, who would think that related to CPU cache side channels?
These are just dumb names for people to share in referring to something. Seems silly and like a waste of time to spend effort getting upset about them.