Java4Shell: RCE in OpenJDK when processing Base64
- lucasluitjes - 703 sekunder sedanFrom the section on performing heap grooming over the network ("Remote Heap Feng Shui"):
> The current attack is sensitive to network conditions, like RTT and jitter. Low, stable round-trip times are preferred for a more reliable attack. In our controlled environment, we performed this attack over the internet through public IP addresses instead of just assuming perfect laboratory conditions. For the current attack path to achieve optimal stability and reliability in exploitation, Calif turned to physics and utilized money to solve the problem, rather than experimenting with TCP/IP stack configuration. In other words, Calif rented another VM in the same region as our target.
And the "Limitations" section:
> There is no universal payload. Each chain needs a decoder route, a live writer, a returned reader or another feedback path, a heap layout, and an application action. Every target needs a bespoke profile. The exploit is not a universal point-and-shoot.
Based on the complexity and constraints, short-term mass-exploitation seems unlikely. It will take some time before there are reliable exploits, and they may require running on infra close to the target.
But a long tail of unpatched java applications/services at high-value targets getting exploited, seems plausible to me.
- ievans - 6700 sekunder sedanSuper impressive work by Calif as usual.
The exploit conditions are very specific but there are still going to be a lot of hosts impacted. We at Semgrep published some free detection scripts here: https://github.com/semgrep/detection-scripts/tree/main/CVE-2...
They look for these five conditions:
* HotSpot VM: any OpenJDK build, Oracle JDK, or GraalVM JDK. Only HotSpot generates the stub. OpenJ9 and GCJ are OK. Azul Prime (Zing), which replaces C2 with its own JIT, and any VM name not recognized as HotSpot are [?], never [!]. * x86-64 JVM on an x86-64 host. * Version 17.0.6 or later, not at or above a version listed in FIXED_IN, and no newer than the newest releases checked (see below). Newer versions are [?]: they may carry the fix. * The JVM reports avx512_vbmi and avx512bw, and UseAVX >= 3. * Base64 intrinsics are on and C2/JVMCI can compile. These turn it off: -XX:-UseBASE64Intrinsics, -XX:DisableIntrinsic=_base64_decodeBlock, -Xint, -XX:TieredStopAtLevel below 4. - leca - 6953 sekunder sedanWhat’s that old Chinese proverb? “May you live in interesting times”? It feels like we’re living in interesting times. How long will it take for a bad actor to seriously compromise critical infrastructure? My bet is within six months.
The upside is that it’ll force legacy institutions and organizations with sub-par security to get good at security and modernize their legacy stacks. That, or get pwned in short order.
- drum55 - 4030 sekunder sedanThey aren’t wrong that we should be deleting more support and removing more features. The idea that the linux kernel by default builds support for all sorts of ancient systems nobody has ever heard of is absurd.
- AgentME - 7624 sekunder sedanUnconfirmed, 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)
- aaronvg - 409 sekunder sedanMakes me wonder whether we would have the same vulnerability if an LLM had written this decoder. It's tricky to write safe hardware accelerated code.
- mzs - 6596 sekunder sedanYou can also mitigate Java4Shell by starting OpenJDK with either:
-XX:-UseBASE64Intrinsics to disable hardware-accelerated Base64 encoding and decoding, or
-XX:UseAVX=2 to disable AVX-512. Apply this flag only on x86-64 hosts. OpenJDK on ARM doesn't recognize it and will fail to start.
- yabones - 5717 sekunder sedanBefore 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.
- nacnud - 5868 sekunder sedanMore 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.
- benjiweber - 7331 sekunder sedan
- hypfer - 5020 sekunder sedanGiven 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?
- rbanffy - 4271 sekunder sedanNot everywhere... Requires an x86-64 processir with AVX512.
- Noe2097 - 3286 sekunder sedanThis attack surface (manually optimized assembly code in the middle of software stacks) looks AWESOME
- kaliszad - 5835 sekunder sedanSeems like -XX:-UseBASE64Intrinsics is the better workaround for now.
- cedricbonhomme - 4313 sekunder sedanTracking sightings related to this vulnerability here: https://vulnerability.circl.lu/vuln/CVE-2026-114938#sighting...
- spidermonkey23 - 1931 sekunder sedanThe string of A's reminds me of the ssh exploit recently.
- plmpsu - 9544 sekunder sedanDoes anyone know what the attack vector of this is? I'm trying to figure out if our usage is affected by this CVE.
- jeffbee - 2322 sekunder sedanIf I owned an entire language platform with a JIT, it would not contain assembly in its standard library, it would simply be improved until it generated something at least that fast from high-level source code on that target CPU.
This is something I really like about LLVM. Their libc isn't spilling over with hand-written assembly. It's written in straightforward C++ under the belief that the compiler does, or will do, a good job.
- cpach - 4963 sekunder sedan.
- titzer - 605 sekunder sedanEncode binary data in text because some dumb thing can't process binary. Text back to binary slow, so better make use of ridiculously wide vector width thing to speed up dumb decoding step we should have never become reliant on in hot paths. Derp, memory safety bug. Derp, die because performance "optimization".
Our incredibly high tower of Jenga blocks is falling down under its own weight.
So many promotions because of optimizing cosmically unnecessary work, though.
Derp, derp, this is humans making computers.
As a person who does these kinds of optimizations, it hits in the feels.
- LastTrain - 559 sekunder sedanSeems like security through obscurity might be a thing after all.
- mushufasa - 4071 sekunder sedanwhere is the dancing girl in the exploit videos???
- DarkmSparks - 2540 sekunder sedanme using java for so long I have my own util.Base64 class used everywhere in pure java.
now panicking in case some LLM imported this without me noticing.
edit: it did. :(
- nikanj - 4986 sekunder sedanJust as with CVE-2026-98432, Debian is immediately patched at embargo drop, Ubuntu still isn't patched.
Why do we even pay for Ubuntu?
- 9029 - 2108 sekunder sedanSo who leaked it?
- iririririr - 4539 sekunder sedanis this why half the banks worldwide are offline on and off since yesterday?
- secondcoming - 4680 sekunder sedanWhy would anyone write the scalar part of a SIMD'd function in assembly code!?
- dboreham - 4901 sekunder sedan"vibe-uncoding" -- have actually been doing quite a bit of that in my older projects.
- doctorpangloss - 6494 sekunder sedanis 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?
- - 6665 sekunder sedan
- - 4911 sekunder sedan
- nassirkhan - 1782 sekunder sedan[flagged]
- Agataproximadev - 1365 sekunder sedan[flagged]
- Sigmazero60 - 6165 sekunder sedanWe set UseAVX=2 on all our jdk hosts last year for unrelated thermal issues, turns out that saved us here
- fidotron - 3567 sekunder sedanThis will almost certainly in practice affect a majority of Java app servers in production.
What makes it nasty is triggering it could be done so easily by url decoding, sending an email or many other things.
- eyalitki - 5931 sekunder sedanThe fact that mainstream modules have such trivial bugs in logic that can be fully covered by testing is staggering. It is about time software developers will have proper test coverage for their code, at least for basic "unit" modules. Maybe we can even name a testing philosophy to match it.
- spullara - 2838 sekunder sedanplease stop using native code that hasn't been proven
Nördnytt! 🤓