It's only on specific architectures though, so it kinda falls apart. It would be impressive if the bug was so portable it let you RCE on sub-AVX512 machines and ARM and whatever too. Maybe with the new vector API we'll see such portable vulnerabilities.
What a horribly written and misleading article. They just make things up to make themselves look good, for example "Memory corruption is the most common class of vulnerability on the Internet". No the fuck it's not? SQL injections is BY FAR the most common class of vulnerability.
This is a much much narrower issue than PHP2Shell.
I like the idea that you're just going to sort of shout down Calif on a point like this. Have you looked at their roster lately?
If you any part of your identity is based on the idea that firms like this aren't finding insane vulnerabilities right now, I think after they find the RCE in OpenJDK's core Base64 processing you're going to have to consider sucking it up, taking the L, and adjusting your priors.
On a simple count like that you could probably beat SQLI on "Javascript prototype pollution", too. But those are 5 classes of vulnerabilities with wildly different impacts, and platform-level SQLI is actually pretty rare.
Is "the most common class of vulnerability" not supposed to be measured by a simple count? It's the blog post's own plain language and it doesn't say anything about impact.
> Is "the most common class of vulnerability" not supposed to be measured by a simple count?
Trivially yes? It'd be a rate of some ilk at least. Upthread, to their credit, was a "score" of undefined nature.
But also, more upthread is talking about "memory corruption", which is going to include far more than just CWE-787. CWEs are a bit weird, and things I'd include in a loose colloquail definition like that would include stack based overflows, heap based overflows (which are for some reason different in CWE land), "classic buffer overflows" (CWE-120, again, their wording), out of bounds writes, OoB reads, null derefs, and use-after-free. All separate CWEs.
lol
This is a much much narrower issue than PHP2Shell.
If you any part of your identity is based on the idea that firms like this aren't finding insane vulnerabilities right now, I think after they find the RCE in OpenJDK's core Base64 processing you're going to have to consider sucking it up, taking the L, and adjusting your priors.
==
Top 10 CWEs (2025 Ranking)
Rank ID Weakness Name Score
1 CWE-79 Cross-site Scripting (XSS) 60.38
2 CWE-89 SQL Injection 28.72
3 CWE-352 Cross-Site Request Forgery (CSRF) 13.64
4 CWE-862 Missing Authorization 13.28
5 CWE-787 Out-of-bounds Write 12.68
Trivially yes? It'd be a rate of some ilk at least. Upthread, to their credit, was a "score" of undefined nature.
But also, more upthread is talking about "memory corruption", which is going to include far more than just CWE-787. CWEs are a bit weird, and things I'd include in a loose colloquail definition like that would include stack based overflows, heap based overflows (which are for some reason different in CWE land), "classic buffer overflows" (CWE-120, again, their wording), out of bounds writes, OoB reads, null derefs, and use-after-free. All separate CWEs.
He's pretty famous in cybersecurity and on HN as a poster.
Yeah, aren't they the ones that jumped the gun on the PHP vuln and published their weird anime PoC video before the embargo expired?
No one's questioning their technical abilities.
Their communication skills are dogshit, however.