News for hackers. Stuff that matters.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by lucasluitjes on Tuesday November 17, 2026 @06:03PM (#50539499)
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.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by jonstewart on Tuesday November 17, 2026 @06:14PM (#50539582)
> Based on the complexity and constraints, short-term mass-exploitation seems unlikely. It will take some time before there are reliable exploits

Mass exploitation, maybe. But LLMs are pretty good at finding exploits now as Calif showed at unprompted a few weeks ago.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by AdrenalinMd on Tuesday November 17, 2026 @06:41PM (#50539839)
Indeed, it can be a SKILL.md that writes the exploit. So in the end it could still be quite mass exploitable, only depends how much context is needed to write the exploit.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by testtestmetest on Tuesday November 17, 2026 @09:48PM (#50541235)
This is not my experience. Great for recon/fuzzing but rather bad at chaining together exploits or creatively making those connections, and you need A LOT of tokens and time to get real results with llms. These capabilities are not within reach for anyone without resources and skills.

But please prove me wrong, if its so easy with an llm theres millions of dollars waiting to be picked up on h1!

Calif gets unlimited tokens from OpenAI to make these findings. Theyre basically the METER operation for OpenAI and scary AI cyber narratives.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by red-iron-pine on Wednesday November 18, 2026 @10:27AM (#50547467)
plenty of nation-state tier actors willing to throw a ton of tokens at the problem

and the level of token require is not out of reach of many business either

Re:Java4Shell: RCE in OpenJDK when processing Base64 by hollerith on Wednesday November 18, 2026 @10:30AM (#50547514)
Businesses however mostly avoid blatantly illegal methods.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by luka2233 on Tuesday November 17, 2026 @06:29PM (#50539708)
still pretty scary for multi-tenant infra
Re:Java4Shell: RCE in OpenJDK when processing Base64 by hinkley on Tuesday November 17, 2026 @08:19PM (#50540650)
Yes but don’t those usually have nginx or friends in front of them? Which apparently frustrates the block size of data being transmitted.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by mschuster91 on Wednesday November 18, 2026 @02:59AM (#50543183)
Well... depending on the application, there might still be code paths in which an attacker can supply b64 to be decoded in a way that can lead to exploitation.

Three years ago, I'd have said, yeah fix the bug but it's so complex to exploit it doesn't need immediate urgency. But now, with AI on the scene? Probably any Java application that somehow accepts user generated input can be exploited for less than a grand in AI token spend.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by afavour on Tuesday November 17, 2026 @06:40PM (#50539828)
Yes, I guess the TL;DR is the chances of a drive by attack are low, but a sufficiently motivated actor with a specific target in mind might be able to exploit it.

So, patch your systems, governments!

Re:Java4Shell: RCE in OpenJDK when processing Base64 by hinkley on Tuesday November 17, 2026 @08:20PM (#50540656)
I’m sure they’re all working late on a Tuesday doing just that. /s
Re:Java4Shell: RCE in OpenJDK when processing Base64 by b800h on Wednesday November 18, 2026 @06:04AM (#50544762)
You'd be surprised, actually.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by lowbloodsugar on Tuesday November 17, 2026 @06:59PM (#50540017)
>Based on the complexity and constraints, short-term mass-exploitation seems unlikely.

Don't see how this is a safe assumption in the modern era of LLMs.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by afavour on Tuesday November 17, 2026 @07:06PM (#50540079)
> The current attack is sensitive to network conditions, like RTT and jitter.

LLMs aren’t magic, they can’t alter physics.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by makeitdouble on Tuesday November 17, 2026 @07:15PM (#50540163)
With only a few major cloud providers, running a VM in physical proximity isn't a herculean task though.

In particular booting a VM is cheap, having them in all potential regions won't break the bank.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by Xirdus on Tuesday November 17, 2026 @07:18PM (#50540186)
Something like 20% of all internet is colocated in us-east-1.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by loloquwowndueo on Tuesday November 17, 2026 @07:57PM (#50540479)
Citation needed.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by codebje on Tuesday November 17, 2026 @08:15PM (#50540621)
Xirdus. (2026, November 18). Something like 20% of all internet is colocated in us-east-1 [Online forum comment]. Hacker News. https://news.ycombinator.com/item?id=50540186
Re:Java4Shell: RCE in OpenJDK when processing Base64 by ChuckMcM on Wednesday November 18, 2026 @01:50AM (#50542725)
And they can't write network code for shit.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by drob518 on Wednesday November 18, 2026 @08:59AM (#50546414)
Obviously, you haven’t read the Anthropic S-1. ;-)
Re:Java4Shell: RCE in OpenJDK when processing Base64 by Uptrenda on Tuesday November 17, 2026 @07:55PM (#50540463)
Are any of these new meme exploits actually exploitable? Do you guys remember when we had human exploits that actually worked...
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.
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.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by saagarjha on Wednesday November 18, 2026 @07:03AM (#50545267)
This is definitely exploitable. The Java heap is not super different than a normal heap in this regard.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by cowlevel on Wednesday November 18, 2026 @08:06AM (#50545861)
this is exactly how so many other exploits already work, it's definitely exploitable, just difficult
Re:Java4Shell: RCE in OpenJDK when processing Base64 by tclancy on Tuesday November 17, 2026 @10:39PM (#50541566)
Are we talking about the five pounds of feathers and five pounds of bowling balls thing?
Re:Java4Shell: RCE in OpenJDK when processing Base64 by tru3_power on Tuesday November 17, 2026 @08:51PM (#50540893)
Decoder route pretty low bar given basic auth right? I think the higher bar is the hardware requirements for exploitation
Re:Java4Shell: RCE in OpenJDK when processing Base64 by neoecos on Tuesday November 17, 2026 @11:17PM (#50541811)
all the cloud providers with x86 use those processors
Re:Java4Shell: RCE in OpenJDK when processing Base64 by darkstar_16 on Wednesday November 18, 2026 @04:19AM (#50543905)
not Azure. The v5 AMD machines for example are Zen 3 as far as I can tell.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by agilob on Wednesday November 18, 2026 @02:46AM (#50543068)
>It will take some time before there are reliable exploits, and they may require running on infra close to the target.

Think that you're targeting KeyCloak and have a semi-working exploit that dumps some parts of heap memory with live tokens. You can go after 100s of banks globally, whole Tesco infra, dozens of gov.uk websites including HMRC and Home Office, azure containers... you know, anyone mature not do write their own auth server: https://www.shodan.io/search?query=keycloak

Re:Java4Shell: RCE in OpenJDK when processing Base64 by theteapot on Wednesday November 18, 2026 @03:49AM (#50543654)
> anyone mature not do write their own auth server

Anyone mature enough not to write their own auth server? I agree with the sentiment.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by ptman on Wednesday November 18, 2026 @05:52AM (#50544649)
Re:Java4Shell: RCE in OpenJDK when processing Base64 by raxxorraxor on Wednesday November 18, 2026 @06:41AM (#50545088)
Just want to nitpick that keycloak is an extremely well auth solution for small to medium sized business as well (at least internally, especially if people spawn a new vibe coded app every other minute).

Also if you are the default Windows shop that uses the common domain controller infra. And no, Entra is not an alternative if you want any client credential flows because then the largest risk becomes your internet connection.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by indigo945 on Wednesday November 18, 2026 @07:18AM (#50545411)
Clearly, the largest risk with Entra is Office361 going down again, which probably happens more often there than with your ISP.

But then, if e-mail and other essential services are down, do you even really care? It's not like you're getting any work done anyhow.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by bradleyjg on Wednesday November 18, 2026 @08:00AM (#50545795)
I’d think that the biggest risk would be Microsoft’s complete indifference to security.

https://www.cisa.gov/sites/default/files/2025-03/CSRBReviewO...

Re:Java4Shell: RCE in OpenJDK when processing Base64 by cbm-vic-20 on Wednesday November 18, 2026 @09:28AM (#50546740)
> Office361

snort

Re:Java4Shell: RCE in OpenJDK when processing Base64 by PantaloonFlames on Wednesday November 18, 2026 @10:39AM (#50547632)
I don’t know why the term Office Tree fitty is not catching on
Re:Java4Shell: RCE in OpenJDK when processing Base64 by red-iron-pine on Wednesday November 18, 2026 @10:25AM (#50547431)
keycloak, jira, confluence, kafka -- lots of potential for fuckery.

a bunch of big attacks got in through secondary paths like that, e.g. the Jag-Land-Rover hacks in the UK started in jira with stolen creds and expanded laterally though PM, tracking, and documentation tools.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by tus666 on Wednesday November 18, 2026 @03:39AM (#50543553)
> Based on the complexity and constraints, short-term mass-exploitation seems unlikely

Haven't you heard of this new fangled thing called AI?

Some people love living under rocks.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by izacus on Wednesday November 18, 2026 @04:05AM (#50543796)
What about this "newfangled AI"? Going into mindless panic over every big security team self-marketing post is not a rational behaviour even with AI.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by cowlevel on Wednesday November 18, 2026 @08:06AM (#50545854)
It's relentless, that's the thing. No human has the persistence to exploit this but you tell Claude Code to do it and come back 3 days and $100000 later and it's done.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by izacus on Wednesday November 18, 2026 @08:08AM (#50545870)
Cool, but still: this has a massive list of ifs and buts to be exploitable that persistence won't fix.

Yes, it needs patching but it's hardly php2shell.

Also last I checked these agents are controlled by people - when's the last time US put anyone to jail for cyber attacks or at least fined them?

Re:Java4Shell: RCE in OpenJDK when processing Base64 by cowlevel on Wednesday November 18, 2026 @10:01AM (#50547125)
Actually this is very analogous to php2shell. That was also extremely difficult to exploit, yet AI got access to a live website within 2 hours and stole their bitcoin.