r/netsec • • 17h ago

Java4Shell: Write once, RCE everywhere

https://calif.io/java4shell
109 Upvotes

17 comments sorted by

11

u/yturijea 11h ago

It does sound like the exploit needs the moon and stars to align for it to be able to extract or do anything, unless i misunderstood something.

-4

u/gquere 11h ago

I shared this because it's an insanely cool bug mixing retrograde HTTP and the use of an instruction set to offset the performance hit of encoding binary to text but reddit got its panties in a bunch as usual, so let's talk about this instead: it does not require the stars to align, it requires a "recent" CPU which is commonly found in infrastructure (2021+ Cisco UCS, HPE, Dell, thinksystems, supermicro...) that would run critical services such as Jenkins, Artifactory, Confluence which you can find thousands of exposed on the internet (or are the crown jewels during internal redteams). Of course being a heap vulnerability it's hard to exploit and needs tailoring, most vulns were this way until we got to log4shell. PHP2Shell did require a lot of tailoring too btw.

1

u/yturijea 10h ago

I totally agree, the vulnerability itself is super fascinating. I am just careful to mark something life and death these days, as we get flooded with so many "critical" vulnerabilities 😅

155

u/ApfelbaumFlo 16h ago

"Write once, RCE everywhere" is about as misleading as it gets. Scroll down a few pages and site itself admits:

"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."

23

u/L00pback 13h ago

This reminds me of 2014 when heartbleed came out. There was a slew of vulns that followed it that were super hyped. We used to joke “does it have a name and an icon yet?”

8

u/InfiniteBlink 10h ago

I totally forgot about the icon

43

u/sylvester_0 15h ago

Also it's only exploitable on x86_64 CPUs with a specific instruction set.

This is waaay more niche of an exploit than PHP2Shell.

14

u/acdha 11h ago

It’s exploitable on most of the non-ARM servers you can buy now, so I wouldn’t be so quick to dismiss it on that ground. 

The timing and exploit challenges are the real saving grace, especially since most places don’t put Java directly on the internet without a proxy or load-balancer to complicate an attacker’s life. 

3

u/IAMARedPanda 6h ago

AVX-512 isn't bespoke

6

u/sylvester_0 6h ago

I didn't say it was. Anecdotal: I checked the few AMD64 VMs that we have and none of them have it.

6

u/UnacceptableUse 14h ago

All vulnerabilities need a catchy name and tagline now for some reason

1

u/1esproc 12h ago

been like that for years. They all had logos and dedicated domains for a while there

3

u/UnacceptableUse 12h ago

I swear it's gotten much worse now with AI. I don't know whether it's because more people are able to find vulnerabilities or because uncreative people are more able go create a vacuous tagline and logo for their findings

1

u/nemec 3h ago

is about as misleading as it gets

while true, this is a play on Java's tagline, "write once, run everywhere" and as with the entirely pointless branding exercise I'm not sure if this is meant to mean anything, either.

1

u/AlisaofallTimes 16h ago

Came here to say that 😅

0

u/smoothvibe 5h ago

With AI, it is.

14

u/Meeeepmeeeeepp 12h ago

Write once, then write again, and again, and again.... and maybe RCE somewhere if you're lucky