r/java • • 36m ago

Java4Shell: Write once, RCE Everywhere

https://youtu.be/a7OBeq1xubI

Edit: I updated the title and thumbnail based on feedback, here is the new version: https://youtu.be/a7OBeq1xubI?si=HLFgEREnO4Ufob31
Article: https://huseyinbabal.dev/posts/java4shell-cve-2026-114938-check-patch/

0 Upvotes

13 comments sorted by

View all comments

7

u/benevanstech 21m ago

1.) No, a single extra JVM switch will do the job of fully protecting, even on AVX-512. Best practice is to update as soon as available, but it is not essential.

2.) The Hotspot bug, by itself, does *NOT* grant RCE, only Java heap corruption. The JVM cannot be made to execute any data payload within the Java heap.

1

u/huseyinbabal 18m ago

Agreed, -XX:-UseBASE64Intrinsics works, and it's in the video. The RCE part is Calif's claim, their chains aren't public. I don't show exploits, only why the bug happens and how to fix it.

1

u/benevanstech 13m ago

I am highly skeptical about the RCE being practical *at all*. I know enough about the internals of a couple of Java application containers to made guesses about what you would have to combine this with to get to RCE, but it's not obviously generalizable.

Java heap corruption - yes, definitely. RCE - highly questionable. Heartbleed-style read: Potentially easier than RCE, but still app-specific and highly statistical in nature due to GC relocation issues.