Hacker News new | past | comments | ask | show | jobs | submit
From 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.

loading story #50543068
loading story #50539582
loading story #50539708
loading story #50539828
loading story #50540893
loading story #50540463
loading story #50542759
loading story #50540017
loading story #50543553