<a href="https://calif.io/java4shell/" rel="nofollow">https://calif.io/java4shell/</a>
Unconfirmed, but people on Twitter suggest this vulnerability has to do with the AVX512 implementation of Base64 decoding, and so this vulnerability can be worked around by running Java with the -XX:UseAVX=2 flag. (<a href="https://x.com/sean_a_cassidy/status/2122791344573976817" rel="nofollow">https://x.com/sean_a_cassidy/status/2122791344573976817</a>)
More info here: <a href="https://www.upwind.io/blog/java4shell-what-we-know-now-and-what-comes-next" rel="nofollow">https://www.upwind.io/blog/java4shell-what-we-know-now-and-w...</a><p>It's a heap out-of-bounds write in Java’s AVX-512 Base64 decoder.
Before you keep your security team up all night, it looks like proxies save the day here. Might not be a complete fix, obviously a real patch should be applied as soon as possible.<p>> Request streaming. Some current grooming profiles need partial request bodies to reach the application. A proxy that waits for the complete body removes their release timing. nginx buffers request bodies by default.<p><a href="https://calif.io/java4shell/#limitations" rel="nofollow">https://calif.io/java4shell/#limitations</a>
<a href="https://github.com/openjdk/jdk/commit/5177a70b385c16f26ede191fdac7aaba0bed0f8b" rel="nofollow">https://github.com/openjdk/jdk/commit/5177a70b385c16f26ede19...</a>
Seems like -XX:-UseBASE64Intrinsics is the better workaround for now.
Does anyone know what the attack vector of this is? I'm trying to figure out if our usage is affected by this CVE.
Some unverified sources have said it's in the Base64 decoder, but strangely only effecting AMD64 machines, so anything on ARM/graviton allegedly isn't impacted. Some sort of bug in some hyper-optimized code I reckon. That might mean any place that parses cookies, headers, urls, JWTs, SAML payloads, certificates, etc, might be exposed. Yikes.<p>But the facts aren't really out yet, we'll learn more in coming hours and days...
No details yet. Calif was supposed to release them at 1PT after the update was pushed out. The corretto release notes say its in hotspot/compiler.<p><a href="https://github.com/corretto/corretto-25/blob/25.0.5.1.2/CHANGELOG.md" rel="nofollow">https://github.com/corretto/corretto-25/blob/25.0.5.1.2/CHAN...</a>
Here's the supposed patch (?): <a href="https://pbs.twimg.com/media/HXWyDZQXEAAPOVf?format=webp&name=large" rel="nofollow">https://pbs.twimg.com/media/HXWyDZQXEAAPOVf?format=webp&name...</a><p>`grep -ow avx512vbmi /proc/cpuinfo | sort -u`<p>`-XX:-UseBASE64Intrinsics -XX:UseAVX=2`
[dead]
is this the root cause of the issue befalling making giant companies right now? i think it's a java DOS for sure, but an RCE?
Looks unrelated, this is being disclosed now but it was discovered a couple of weeks ago and is just now being made public at the same time.<p>Also I haven't looked into it, but I'm willing to be it's some free after-use memory corruption thing that has a CVSS Attack Complexity of high, the 'RCE' is speculative, and private companies push social media headlines to fit the AI cybersecurity narrative.<p>Not saying the doom isn't right, but sometimes it's more like a Wednesday than doomsday. Just patch it and move on. Thanks to all involved though in disclosing and patching though.