NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
▲Java4Shell: RCE in OpenJDK when processing Base64 (calif.io)
ievans 1 hours ago [-]
Super 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.
drum55 18 minutes ago [-]
They 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.
leca 1 hours ago [-]
What’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.

ctoth 19 minutes ago [-]
> My bet is within six months

My bet is it already happened two months ago and there's a whole secret scrum we only vaguely know about happening right now.

adrianpike 5 minutes ago [-]
Instability is often correlated to urgently performed change, and we've seen a lot of instability around the world lately.
Noe2097 6 minutes ago [-]
This attack surface (manually optimized assembly code in the middle of software stacks) looks AWESOME
juliusdaniel7 6 minutes ago [-]
[dead]
mzs 1 hours ago [-]
You 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.

layer8 6 minutes ago [-]
Note that -XX:-UseBASE64Intrinsics requires -XX:+UnlockDiagnosticVMOptions to work.
marginalia_nu 54 minutes ago [-]
Might be worth examining whether AVX-512 is even supported on the machine before freaking out, too.
fidotron 11 minutes ago [-]
This 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.

cpach 34 minutes ago [-]
ryanschaefer 27 minutes ago [-]
This should be the main thread as this is the primary source
rbanffy 22 minutes ago [-]
Not everywhere... Requires an x86-64 processir with AVX512.
formerly_proven 14 minutes ago [-]
Pretty much any Intel server and most AMD servers are going to support AVX512 and conversely most VMs running in the cloud will have access to it.
rbanffy 54 seconds ago [-]
Speak for yourself. All my cloud VMs are ARM, with one exception, one s390x running Linux.
mushufasa 19 minutes ago [-]
where is the dancing girl in the exploit videos???
secondcoming 29 minutes ago [-]
Why would anyone write the scalar part of a SIMD'd function in assembly code!?
magackame 12 minutes ago [-]
pure love for the game
nikanj 34 minutes ago [-]
Just as with CVE-2026-98432, Debian is immediately patched at embargo drop, Ubuntu still isn't patched.

Why do we even pay for Ubuntu?

cpach 23 minutes ago [-]
Are you sure? I can’t see any Debian advisory for this vuln.

https://www.debian.org/security/

13 minutes ago [-]
48 seconds ago [-]
dboreham 33 minutes ago [-]
"vibe-uncoding" -- have actually been doing quite a bit of that in my older projects.
Sigmazero60 54 minutes ago [-]
We set UseAVX=2 on all our jdk hosts last year for unrelated thermal issues, turns out that saved us here
eyalitki 50 minutes ago [-]
The 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.
Noe2097 23 minutes ago [-]
Not sure this is as trivial as it seems. The bug triggers on a specific instruction set, on a precise input length, with a specific character at the end, and when on the hot path, and requires low level memory access checking to be detected.
ajasmin 27 minutes ago [-]
Finding these kind of bugs would have required fuzzing and some kind of bound checking canaries. Not sure all bound checkers work on the hand-optimized assembly.

Or as it turns out an LLM! Not clear whether their agent spawned any classic tools...

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 22:26:29 GMT+0000 (Coordinated Universal Time) with Vercel.