logoalt Hacker News

vbezhenar • today at 2:15 AM • 5 replies • view on HN

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.


Replies

guipsp • today at 4:39 AM

You can read the article to understand how heap layout is made more predictable.

➕ show 1 reply
saagarjha • today at 12:03 PM

This is definitely exploitable. The Java heap is not super different than a normal heap in this regard.

cowlevel • today at 1:06 PM

this is exactly how so many other exploits already work, it's definitely exploitable, just difficult

worthless-trash • today at 7:33 AM

Attacker controlled writes along with heap grooming allows for exploitation. Very common practice.

asdf88990 • today at 3:15 AM

So at least DOS is possible?

➕ show 1 reply