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.
Some more discussion: https://news.ycombinator.com/item?id=50538240
Comments moved thither. Thanks!
https://calif.io/java4shell/
> Write once, RCE everywhere
lol
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.
Sure, but X86 has an enormous market share though.
Vulnerable platforms make up the overwhelming majority of all serverside Java applications.
At least on the AMD Epyc side you need a CPU that's no older than 2023 to be vulnerable. Naples, Rome and Milan are all AVX2-only.
That's a good corrective, thank you!
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.
The tone wasn't great, but hard to argue on the facts:
==
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
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.
> Have you looked at their roster lately?
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.
I believe that was Chainguard, wasn't it?