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. (https://x.com/sean_a_cassidy/status/2122791344573976817)
Given that this is AVX512-only...how many enterprises are out there that run vulnerable java applications on non-intel servers?
Genuine question. Everything I see is Intel all the time. I know that people at home switched to AMD, but they don't run enterprise java.
I also have been told that apparently EPYC was hyped for a while and some hosters give you that. But do corporations run the java applications there?
The name makes it sound like Log4J or the PHP thing, but from what I can tell right now, it kinda isn't all that relevant?
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.
> 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.
More info here: https://www.upwind.io/blog/java4shell-what-we-know-now-and-w...
It's a heap out-of-bounds write in Java’s AVX-512 Base64 decoder.
Does anyone know what the attack vector of this is? I'm trying to figure out if our usage is affected by this CVE.
Seems like -XX:-UseBASE64Intrinsics is the better workaround for now.
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?
https://calif.io/java4shell/