Re:Java4Shell: RCE in OpenJDK when processing Base64
by vbezhenar on Tuesday November 17, 2026 @09:15PM
(#50541026)
Can't see it exploitable. You're writing some bytes after the allocated object memory. Java objects live in heap. The order will be completely undefined and GC moves objects around. So the best case you just write some bytes into next object, corrupting it in some way. There are millions of objects in any Java program and the program behaviour will be completely non-predicatable if you corrupt the objects. Most likely JVM will eventually crash if you corrupt object header.
[ Parent
| on HN ]
Re:Java4Shell: RCE in OpenJDK when processing Base64
by asdf88990 on Tuesday November 17, 2026 @10:15PM
(#50541415)
So at least DOS is possible?
Re:Java4Shell: RCE in OpenJDK when processing Base64
by agilob on Wednesday November 18, 2026 @02:48AM
(#50543083)
Causing OOM should be rather trivial.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by guipsp on Tuesday November 17, 2026 @11:39PM
(#50541939)
You can read the article to understand how heap layout is made more predictable.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by kimi on Wednesday November 18, 2026 @03:51AM
(#50543672)
"More predictable" != "predictable". This said, even a remote crash 1 time out of 1M request is significant.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by worthless-trash on Wednesday November 18, 2026 @02:33AM
(#50542979)
Attacker controlled writes along with heap grooming allows for exploitation. Very common practice.