Re:Java4Shell: RCE in OpenJDK when processing Base64
by leca on Tuesday November 17, 2026 @04:19PM
(#50538337)
What’s that old Chinese proverb? “May you live in interesting times”? It feels like we’re living in interesting times. How long will it take for a bad actor to seriously compromise critical infrastructure? My bet is within six months.
The upside is that it’ll force legacy institutions and organizations with sub-par security to get good at security and modernize their legacy stacks. That, or get pwned in short order.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by pixl97 on Tuesday November 17, 2026 @05:32PM
(#50539212)
A lot of organizations we sitting on internal bugs for years because they thought they were impossible to exploit, and now their red team can break them in hours.
Most businesses are stuck in a trap now. They know the software is exploitable, but they are organizationally slow in testing and rollout. They have to start moving fast with security and IT organizations that are cut to the bone, yet at the same time contain to much box checking deadweight.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by thephyber on Tuesday November 17, 2026 @08:27PM
(#50540705)
I don't think AI slop code is the proximal cause for most of this. It is, however, the most common meme for blame.
My suspicion is (1) company execs are being told to expect company extinction if they don't force faster velocity and (2) we are increasingly building more and more complex systems, so neither AI nor humans can find all of the issues before they cause outages.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by Analemma_ on Tuesday November 17, 2026 @05:35PM
(#50539251)
I think this bet is optimistically assuming a far more competent world than the one we actually have. Have you seen the idiot clowns actually in power? The agency that might've been tasked with this hypothetical secret scrum, CISA, has been gutted and left to rot because they thought it was an enemy plot to censor them on social media or whatever. There's no smoky room where the smart people are fixing things.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by jeremyjh on Tuesday November 17, 2026 @06:39PM
(#50539818)
There is no secret room where smart people people aligned with the interests of the people of the United States are fixing things, because we selected a criminal syndicate to provide our governance until the end of 2028. By then there there may be nothing left to fix.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by makeitdouble on Tuesday November 17, 2026 @07:22PM
(#50540216)
We've already seen an attack on transfusion blood storage.
I wouldn't minimize the impact of the ones on supermaket freezers either. It was technically dumb and somewhat laughable, but we're talking food. The affected chains had stores in very rural areas with elder people living in remote places, these supermakets would be the only purveyor of long conservation food.
I'd argue we're already there, albeit at small scale yet.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by makeitdouble on Wednesday November 18, 2026 @12:48AM
(#50542337)
Preportioned meals that are hot and ready at the push of a button is a godsend for people with disabilities and/or entering older age. Someone buying a few dozen of those can be set for weeks, longer if they also continue cooking simple dishes from time to time when they feel good. This helps tremendously to keep them independent and self sufficient.
Someone coming once every month to the supermaket to restock, only to be told there's only fresh and canned food available must feel devastated IMHO.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by account42 on Wednesday November 18, 2026 @07:16AM
(#50545385)
Those people can eat raw veggies other raw ingredients until the store fridges are re-stocked. And there are also plenty of just-add-water ready meals that don't need any refrigeration. No ones survival depends on frozen food.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by account42 on Wednesday November 18, 2026 @07:17AM
(#50545402)
Not all things that are done are actually needed. Eggs survive for weeks without refrigeration too if you don't destroy their natural protective layer for example.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by testtestmetest on Tuesday November 17, 2026 @07:39PM
(#50540340)
That's what they want you to expect. Either way, the worst possible people on our side will take advantage of it, and possibly cause it for that opportunity.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by nedt on Wednesday November 18, 2026 @08:48AM
(#50546276)
No single exploit should be able to take down critical infrastructure. If it does the setup is broken. Security is layers around it and the layers shouldn't trust each other nor should they be fully depended on them.
* HotSpot VM: any OpenJDK build, Oracle JDK, or GraalVM JDK. Only HotSpot generates the stub. OpenJ9 and GCJ are OK. Azul Prime (Zing), which replaces C2 with its own JIT, and any VM name not recognized as HotSpot are [?], never [!].
* x86-64 JVM on an x86-64 host.
* Version 17.0.6 or later, not at or above a version listed in FIXED_IN, and no newer than the newest releases checked (see below). Newer versions are [?]: they may carry the fix.
* The JVM reports avx512_vbmi and avx512bw, and UseAVX >= 3.
* Base64 intrinsics are on and C2/JVMCI can compile. These turn it off: -XX:-UseBASE64Intrinsics, -XX:DisableIntrinsic=_base64_decodeBlock, -Xint, -XX:TieredStopAtLevel below 4.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by cjbprime on Tuesday November 17, 2026 @05:36PM
(#50539263)
Wouldn't it be prudent for someone to patch even if they aren't running their code on an AVX512 system right this moment? They could be running on one.. next moment.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by stackskipton on Tuesday November 17, 2026 @05:55PM
(#50539423)
Depends on the company and deployment method. As Ops person, I generally don't think much about rolling out different Kubernetes Nodes and what SKU I select. So yes, you could be running on one node type today and tomorrow I upgrade the nodes under you.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by xmodem on Tuesday November 17, 2026 @06:42PM
(#50539846)
We’re using a second-tier cloud provider’s managed Kubernetes offering, and in investigating our level of exposure to this, I just learned that there is variance within a node pool on whether AVX-512 is available.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by jamesfinlayson on Tuesday November 17, 2026 @11:47PM
(#50541993)
This - I remember taking a suggestion to cat cpuinfo as part of container start in AWS and you do get a bit of variety as you'd expect (five year old processors last time I checked as well).
Re:Java4Shell: RCE in OpenJDK when processing Base64
by Sohcahtoa82 on Tuesday November 17, 2026 @06:39PM
(#50539816)
> Or, do running machines often have their CPU changed from under them without much notice?
I dunno about other cloud providers, but I know AWS can move your EC2 VM from one system to another transparently. There is a server ID you can get from the metadata, but unless you're checking it frequently, you can be moved without ever being aware.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by PhilipRoman on Tuesday November 17, 2026 @07:11PM
(#50540131)
Question is if they expose it to the guest. Many (most?) cloud platforms will make the guest see the lowest common denominator, specifically to avoid angry customers when their working setup suddenly breaks.
In the case of transparent migration, I think it's basically a must. No JIT (or even libc probably) is going to support CPU features changing at runtime.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by Sohcahtoa82 on Wednesday November 18, 2026 @02:00AM
(#50542789)
Not true.
AWS migrates live instances to new CPUs without needing to stop or reboot the guest.
When a migration is needed, the hypervisor begins copying blocks of memory to the new system, keeping track of what blocks are written inside the guest during the migration. Once enough has been copied, it hibernates the guest, copies the remaining memory, then wakes it in the new system. On a system that isn't writing to large swaths of memory, it can take only a few milliseconds. To the guest, it might appear that the CPU froze for a tiny bit of time, which could easily just look like a neighbor got noisy.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by mike_hearn on Wednesday November 18, 2026 @03:10AM
(#50543278)
Yes, but that's irrelevant here because the CPUID report won't change across live migrations.
Consider what would happen if you were live migrated from a machine with AVX512 to one without. Your app would suddenly start crashing with SIGILL for no apparent reason. So, live migrations always preserve the apparent CPU feature set. If you started on a machine without AVX512 then until the VM is rebooted you will remain on such a (virtual) machine.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by bonsai_spool on Tuesday November 17, 2026 @05:36PM
(#50539270)
This looks like Claudese - may be kind to write such things yourself if you intend for humans to read them. (For example, “ HotSpot VM: any OpenJDK build, Oracle JDK, or GraalVM JDK. Only HotSpot generates the stub. OpenJ9 and GCJ are OK. Azul Prime (Zing), which replaces C2 with its own JIT, and any VM name not recognized as HotSpot are [?], never [!].” — I tried parsing at least five times before realizing you’re asking me to decipher LLM talk)
Re:Java4Shell: RCE in OpenJDK when processing Base64
by kaboberg on Tuesday November 17, 2026 @06:45PM
(#50539883)
Azul Core definitely is - it uses upstream HotSpot.
Azul Platform Prime (formerly Zing) may or may not be depending on whether they touched the base64 intrinsic. Since it is closed-source there is no way to verify via code, which is how our research team investigates ecosystem events like this.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by stevenhuang on Wednesday November 18, 2026 @05:21AM
(#50544398)
What's with this weird tendency to think everything you don't immediately understand is LLM? It's okay to not understand things. Have you worked with Java at all? Why do you expect to make sense of those technologies if not?
I've done Android development and there's nothing wrong with the way it's phrased. All of that is high signal information.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by bikezen on Tuesday November 17, 2026 @05:40PM
(#50539305)
The write-up itself matches your version assumption, however it also says:
> According to Oracle, the following Oracle Java SE versions are vulnerable: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3. We thank Oracle for providing this information ahead of publication time.
So according to Oracle at least, JRE8 versions are affected as well.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by looperhacks on Wednesday November 18, 2026 @12:41AM
(#50542298)
It's a bit of a mess. The first four are for the jvm, shared across all implementations: $FEATURE.$INTERIM.$UPDATE.$PATCH
$FEATURE: increased every six months when new features are released (or removed)
$INTERIM: currently always 0, reserved for future use
$UPDATE: non-feature releases like bug, security or regression fixes. Releases one month after the feature version; then every three months
$PATCH: important updates out of schedule
Specific implementations may introduce a fifth component for updates that do not come from the shared implementation but are distribution-specific (think Oracle fixing a bug that only happens in Oracle distributions)
(Then there's more, like +2 build numbers, and older versions have a slightly different format)
Re:Java4Shell: RCE in OpenJDK when processing Base64
by thephyber on Tuesday November 17, 2026 @08:01PM
(#50540521)
Oracle owns Java and Oracle is "OpenAI funded" in the sense that Oracle's data center buildouts are being done using OpenAI as a consumer.
The circular financing continues!
But seriously, the funding here doesn't matter any more than Project Zero's funding comes from Google. Big companies are trying to improve security for the common software substrates of our industries / governments.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by yburkov on Wednesday November 18, 2026 @08:07AM
(#50545869)
one note: it means -XX:-UseBASE64Intrinsics OR XX:DisableIntrinsic=_base64_decodeBlock OR -Xint OR -XX:TieredStopAtLevel below 4 (-XX:TieredStopAtLevel=3 and so on)
Re:Java4Shell: RCE in OpenJDK when processing Base64
by eyalitki on Tuesday November 17, 2026 @04:36PM
(#50538534)
The fact that mainstream modules have such trivial bugs in logic that can be fully covered by testing is staggering. It is about time software developers will have proper test coverage for their code, at least for basic "unit" modules. Maybe we can even name a testing philosophy to match it.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by ajasmin on Tuesday November 17, 2026 @04:59PM
(#50538825)
Finding these kind of bugs would have required fuzzing and some kind of bound checking canaries. Not sure all bound checkers work on the hand-optimized assembly.
Or as it turns out an LLM! Not clear whether their agent spawned any classic tools...
Re:Java4Shell: RCE in OpenJDK when processing Base64
by Noe2097 on Tuesday November 17, 2026 @05:03PM
(#50538873)
Not sure this is as trivial as it seems. The bug triggers on a specific instruction set, on a precise input length, with a specific character at the end, and when on the hot path, and requires low level memory access checking to be detected.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by spockz on Tuesday November 17, 2026 @05:43PM
(#50539329)
For the finished jre yes. But one would hope these kind of checks are also run on a hand rolled decoder function. Fuzzing that one and finding logic bugs is a lot easier
Re:Java4Shell: RCE in OpenJDK when processing Base64
by jamesfinlayson on Wednesday November 18, 2026 @01:25AM
(#50542546)
Extra speed I assume.
I saw some assembly in code at work for various hot path stuff but it was all written before the last version control move. The 64-bit stuff was just done in plain C though which was probably good enough by the time it needed to updated to build as 64-bit.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by looperhacks on Wednesday November 18, 2026 @09:15AM
(#50546584)
I tried to reproduce it on AWS (for a before/after comparison to prove the mitigation), but I couldn't. Either the reproducer from TFA doesn't work, or Fargate placed it on CPUs that don't support the instructions.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by drum55 on Tuesday November 17, 2026 @05:08PM
(#50538933)
They aren’t wrong that we should be deleting more support and removing more features. The idea that the linux kernel by default builds support for all sorts of ancient systems nobody has ever heard of is absurd.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by Gigachad on Tuesday November 17, 2026 @07:23PM
(#50540239)
The kernel already dynamically loads kernel modules based on hardware it's running on so most of the junk isn't loaded. But for the stuff you can't dynamically load, it's a tradeoff between stripping the kernel down and supporting the most hardware.
Maybe distros could provide two builds, one for modern hardware only and one for maximum compatibility.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by cheeze on Tuesday November 17, 2026 @11:57PM
(#50542058)
Back in the day, I used to build windows XP as stripped down as possible. Maybe something like that is possible? Distro installer determines what hardware you're running, then only includes what is absolutely necessary?
More annoying the first time you plug in that USB DAC or whatnot, but would reduce the attack surface heavily.
Who am I kidding... someone is going to comment that Dolphin Linux has supported this since 2013.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by Gigachad on Wednesday November 18, 2026 @12:30AM
(#50542244)
You have to compile the kernel to change the included features. You can certainly do that and some people have been running stripped back kernels for a long time but you can imagine why mainstream distros don’t make you do that.
Before recently kernel security was relatively acceptable.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by rustyhancock on Wednesday November 18, 2026 @06:29AM
(#50544987)
Back in the mid-2000s I regularly simply built a kernel to match what I was running daily, and kept a stock generic kernel.
I started it in freebsd and later on Linux.
I'm not quite sure why I stopped the practice if I'm honest probably because generic felt good enough at some point and I forgot. Probably because my peripheral use became more chaotic.
That and most of the benefit is RAM footprint which stopped mattering.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by xxs on Wednesday November 18, 2026 @02:08AM
(#50542847)
Java has lots of it, even crc32 has a similar loop.
Few years back I had to manually inspect the crc32 loop (due to gzip warnings) when it was used on unalign arrays. It was ok.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by xxs on Wednesday November 18, 2026 @10:00AM
(#50547102)
I don't understand the point.
Yes, JIT has lots of intrinsics.I had to inspect the crc32 loop (128bit vector instructions) as I expected to be faulty in some cases of unaligned data but it was fine.
I am very much aware where the assembly code for Hotspot is.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by DarkmSparks on Wednesday November 18, 2026 @03:25AM
(#50543420)
built for java 6, built in one didnt come to java 8, never noticed.
Now it has lots of other little functions, like inline AES256 encryption/decryption and different functions names (like encode lines for b64 split over lines).
Re:Java4Shell: RCE in OpenJDK when processing Base64
by jeffbee on Tuesday November 17, 2026 @05:36PM
(#50539268)
If I owned an entire language platform with a JIT, it would not contain assembly in its standard library, it would simply be improved until it generated something at least that fast from high-level source code on that target CPU.
This is something I really like about LLVM. Their libc isn't spilling over with hand-written assembly. It's written in straightforward C++ under the belief that the compiler does, or will do, a good job.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by jamesfinlayson on Wednesday November 18, 2026 @01:27AM
(#50542565)
> If I owned an entire language platform with a JIT, it would not contain assembly in its standard library, it would simply be improved until it generated something at least that fast from high-level source code on that target CPU.
Interestingly I remember a guy who worked on the JVM giving a talk and saying (back then at least) that they were working to move as much of the JVM to plain Java as they could.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by saagarjha on Wednesday November 18, 2026 @07:13AM
(#50545355)
I don’t think you’ve looked at LLVM libc’s string routines if you think it’s “written in straightforward C++ under the belief that the compiler does…a good job”. It’s basically an assembly DSL
Re:Java4Shell: RCE in OpenJDK when processing Base64
by jeffbee on Wednesday November 18, 2026 @09:57AM
(#50547070)
I think I know vaguely what you mean. But LLVM still tries to contain the asm to the minimal, innermost performance-sensitive place where it needs to go, if it needs to be there at all, and they use intrinsics whenever possible instead of asm statements. Compare LLVM and GNU strlen. In LLVM, the logic of the function is mostly in readable code, and the way to select the target ISA makes sense. In GNU, it's 100% assembly and the target ISA is involved in scattered preprocessor directives.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by rb12345 on Wednesday November 18, 2026 @03:54AM
(#50543694)
That doesn't surprise me. Long strings of "A"s are the traditional way of finding/triggering buffer overflows as they're easy to spot in the memory dumps.
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 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 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.
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 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 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 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 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 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.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by titzer on Tuesday November 17, 2026 @06:05PM
(#50539508)
Encode binary data in text because some dumb thing can't process binary. Text back to binary slow, so better make use of ridiculously wide vector width thing to speed up dumb decoding step we should have never become reliant on in hot paths. Derp, memory safety bug. Derp, die because performance "optimization".
Our incredibly high tower of Jenga blocks is falling down under its own weight.
So many promotions because of optimizing cosmically unnecessary work, though.
Derp, derp, this is humans making computers.
As a person who does these kinds of optimizations, it hits in the feels.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by layer8 on Tuesday November 17, 2026 @07:51PM
(#50540434)
Your decoder implementation accepts all sorts of non-Base64 strings and decodes them to whatever. Among other things, it also accepts MIME Base64 (with line breaks and whitespace) and base64url strings, but decodes them to the wrong values. This is a classic example of insufficient input validation that can lead to parser mismatch vulnerabilities or worse.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by fsnovask on Tuesday November 17, 2026 @06:43PM
(#50539855)
>The best hacker today is neither AI nor human. It is the centaur hacker, part human, part AI.
I think only really smart people are going to be left in Security and Software. I can barely fathom what this group is doing with AI right now (ignoring that their model probably isn't nerfed) and I don't think any of this is trainable. This is starting to feel like some of the scientific fields where careers start when you get a MS/PhD. Or like the average developer now can't convert a Word document to PDF.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by antonvs on Tuesday November 17, 2026 @11:49PM
(#50542001)
Chess is very constrained, and doesn't require all sorts of knowledge about the broader context outside the game.
Once models are more hooked up to sources of information, their capabilities will improve. Currently, humans are a bottleneck for providing the information relative to specific problems.
"Take the human out of the loop" - I think there was a documentary about that, with Matthew Broderick.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by eru on Tuesday November 17, 2026 @06:55PM
(#50539972)
> I think only really smart people are going to be left in Security and Software.
I'm looking forward to eventually getting there. At the moment, there's so much low hanging fruit that even someone without a clue like me can just point a fuzzer at some random Linux kernel code and still discover problems.
(Most of the problems I found from that exercise are patched by now, if you use a recent enough kernel.)
I used Kimi to drive the fuzzer. The model didn't have to do anything smart, just do the tedious work of writing the glue code to make the fuzzing work. AFL++ did the 'smart' parts, and I had the idea to kick it off and oversaw the patches.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by Pokepokalypse on Tuesday November 17, 2026 @11:22PM
(#50541842)
Truth be told; as far as I can tell, the output the human gets from the AI can vary vastly in quality, depending on guardrails on the AI side. Guardrails that are internal (and opaque) to the user, combined with directives the user sets up, often manually.
(for example, I have mine keep ready reference to all of our CMMC controls and best practices)- and not only will my sessions cite referenced material as it responds, but it will do so when it writes code, as well - and it does a pretty decent job of keeping me honest. The one bit I'm struggling with is limiting complexity when it designs a solution to a problem. For larger projects, this can snowball quickly - and I haven't found an effective way to prevent this yet.
Skills can be shared, but it's a bit of a steep climb to getting an entire organization to pick the same skill (to get consistent behavior across the whole org)- sometimes an individual skill as it's written, will conflict with some other personal standard or quirk of how they work, so it's difficult to share them. This really seems, to me, to be very similar to how the software world used to work (as far as interoperability goes), earlier in history when there weren't many open standards, (and NO open source code) - and every competing OS vendor was trying to destroy their competitors so they could become a monopoly.
But yes, there's quite a bit of effort now that goes into maintaining this personal harness, and I'm sure the even smarter folks will come along and figure out workable ways of standardizing and sharing those kinds of harnesses.
I've been in this industry for 30 years, and the way I work has always changed with the times and new tools. It changed a LOT when Dev Ops became a thing. IaC, and containers. This feels kind of like that change, but maybe an order of magnitude. Almost feels like going from assembler to learning something like python; in terms of how much abstraction is being added.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by EGreg on Tuesday November 17, 2026 @07:54PM
(#50540460)
For anyone who cares, I have a solution "for now".
When PHP2shell was announced, before the patches were available, I wrote a proxy to sanitize input. You should have an input-sanitizing proxy in front of your app servers anyway instead of waiting for patches for as-yet-undiscovered CVEs.
PHP < 8 doesn't have patches coming. It's either the proxy or be pwned. Some our honeypot machines running PHP 5 got infiltrated with full chained kernel-level exploits. The ones with the proxy didn't. Which one do you want to be?
Having said that, my proxy approach wouldn't fully protect ALL Java apps in this case, because:
A Java program that opens a TLS connection to a malicious server can be compromised, even if it exposes no service of its own.
The problem is that you can't intercept and "heal" TLS connections with a proxy, unless you also spoof the TLS certificates. However, since most Java apps don't pin certs, a workaround is using /etc/hosts and a CA cert added in cacerts. Then the proxy approach works even on outbound traffic. And you don't have to wait for the patches.
1. Add maliciousserver.com -> 127.0.0.1 (or proxy IP) in /etc/hosts
2. Java app resolves the hostname, connects to your proxy on 443
3. Proxy presents a cert for maliciousserver.com signed by your local CA
4. JVM checks: right hostname, trusted CA? handshake succeeds
5. Proxy connects to the real server (using its own resolver that bypasses /etc/hosts, or the real IP directly)
6. Normalizes Base64 in the response (assuming Calif relies on a wacky base64)
7. Relays to Java client (safe)
so what you'd do is:
1. Generate proxy CA cert
2. Install in JVM truststore (keytool)
3. /etc/hosts entries for known hostnames
4. forward_proxy config block (port, ca_cert, ca_key)
5. You have three options for routing:
HTTPS_PROXY env,
JVM flags (-Dhttps.proxyHost),
or iptables REDIRECT (covers code that ignores proxy vars)
6. Start qbixproxy
7. Verify with curl
The usual disclaimers... lock down the executable, removing any ability to read or write files, only pass traffic through like a proxy. Investigate the repo yourself, with your own Claude or ChatGPT etc. The repo even has links to pre-fill the prompts to do just that.
I'm putting this out under MIT license to help people, but under this license it disclaims all warranties, including implied warranty for merchantibility etc.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by ozgrakkurt on Wednesday November 18, 2026 @08:33AM
(#50546120)
From what I understood it is generated by the JIT compiler and they don't fuzz JIT compiler output.
I am fairly sure it should still be possible to fuzz this by fuzzing the jit compiler. I understand it is not as easy as just fuzzing a regular function though.
It is even easier than fuzzing the JIT compiler in this case imo since it just inserts a fixed block of code which can be fuzzed seperately.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by vips7L on Tuesday November 17, 2026 @10:49PM
(#50541638)
It was fixed in Azul and Corretto this morning. Eclipse is notorious for slow rolling patches. It’s sad that they convinced a large number of people to run Temurin.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by ethagnawl on Tuesday November 17, 2026 @09:09PM
(#50540988)
That Vibe Uncoding section didn't go where I thought it was going. Instead of suggesting people stop vibe coding and potentially introducing more/new vulns, they suggest vibing the removal of features and hoping the model or the tests it generated or whatever catch the edge cases. It really does feel like we're circling the drain here, folks.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by ulrikrasmussen on Wednesday November 18, 2026 @05:22AM
(#50544410)
The tag line "Write once, RCE everywhere" is also annoying. I get the reference, but the article explicitly says there is no generic exploit and that it probably isn't possible to make one. That's pretty much the opposite message from the tag line.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by sabretooth1405 on Tuesday November 17, 2026 @11:23PM
(#50541851)
I see no security advisory from Elasticsearch yet,we operate multiple ES clusters and I am not exactly sure what the mitigation is here. Changing our JVM options and restarting the nodes?
Re:Java4Shell: RCE in OpenJDK when processing Base64
by CountVonGuetzli on Wednesday November 18, 2026 @08:39AM
(#50546188)
Yeah I'm a bit annoyed at them for not sharing any information with us (we use the managed version).
After checking, we discovered that they are using version 26, which is a non-lte version that hasn't received patches since March 2026, and also that our cluster runs on ARM64, which is not affected by the vulnerability.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by tomekb on Wednesday November 18, 2026 @12:51AM
(#50542353)
This looks like it requires G1? ZGC, ParallelGC or Serial are not affected? Smaller workloads running on singe CPU containers would default to Serial GC.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by tesnorindian on Wednesday November 18, 2026 @01:02AM
(#50542417)
Vibe uncoding should be the way forward to prevent these bugs. LLMs should strip and bake our apps with only those required features and libraries to reduce the blast radius instead of affecting everyone. LLMs are not only good with vibe coding but also aka. vibe uncoding.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by Woodi on Wednesday November 18, 2026 @01:25AM
(#50542543)
Uuuu, bug and exploits part is pretty standard so becomes boring wall of text that is instantly obsolete after patches, I hope ;) And no animation ?? How hard it is to splash there some animation ?? ;)
But there is part of article that somehow nobody mentions ! "A call for vibe-uncoding" and that is a future and sane sanity. How many unused Linux modules laying on disk ? And more commercial systems are usually worse - installer just unpacks and declares warranty void if something is modified or removed - law enforced stupidity.
You have [open] code ? You can clean it by doing very coarse work of not calling unused code or hardcoding return error on calling unused parts.
Like FTP code. Open source IT declared it dead years ago but camera and game manufacturers and probably more industries didn't get a memo. Still we do not implemented ftp replacement and ssh is single point of failure.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by badgersnake on Wednesday November 18, 2026 @01:57AM
(#50542770)
Leaving aside the vulnerability, this is a terrible blog post. Even the title is wrong (RCE anywhere, no only on x86). The smug tone and the LLMese makes me want nothing to do with this mob.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by zkmon on Wednesday November 18, 2026 @02:05AM
(#50542826)
The risk owners, security teams, compliance teams - are all holding tight inside a tent built for the usual weather, but facing an un-announced storm now.
Their first priority is not stabilizing the tech tent. They are busy planning the risk distribution, risk outsourcing, legal prep, customer messaging, ToS/SLA reviews, contracts etc. They are reinforcing the good-old fort walls around the tech tent.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by ad_hockey on Wednesday November 18, 2026 @05:44AM
(#50544587)
Yeah, it's a term from automation theory. I don't know how old it is, but Kasparov was talking about centaur chess (humans paired with AIs) back in 2017[1].
It got a lot more popular recently when Cory Doctorow started talking about "reverse centaurs", where the job of the human is to assist the AI.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by djha-skin on Wednesday November 18, 2026 @08:13AM
(#50545911)
> It took our own Quang Luong an hour to discover the vulnerability, and two more hours to develop the first working exploit. The total token cost was less than $200.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by jrmg on Wednesday November 18, 2026 @09:36AM
(#50546819)
Their video of the exploit in action would be stronger if it was a bit more straightforward.
All the (impressive!) distracting graphics, the speed of change, and the lack of commentary meant it took me a few watches to actually notice the ‘seashell’ segments were wrapping remote shells that the exploit had given them.
The upside is that it’ll force legacy institutions and organizations with sub-par security to get good at security and modernize their legacy stacks. That, or get pwned in short order.
My bet is it already happened two months ago and there's a whole secret scrum we only vaguely know about happening right now.
Most businesses are stuck in a trap now. They know the software is exploitable, but they are organizationally slow in testing and rollout. They have to start moving fast with security and IT organizations that are cut to the bone, yet at the same time contain to much box checking deadweight.
My suspicion is (1) company execs are being told to expect company extinction if they don't force faster velocity and (2) we are increasingly building more and more complex systems, so neither AI nor humans can find all of the issues before they cause outages.
I wouldn't minimize the impact of the ones on supermaket freezers either. It was technically dumb and somewhat laughable, but we're talking food. The affected chains had stores in very rural areas with elder people living in remote places, these supermakets would be the only purveyor of long conservation food.
I'd argue we're already there, albeit at small scale yet.
Someone coming once every month to the supermaket to restock, only to be told there's only fresh and canned food available must feel devastated IMHO.
That happened when Colonial Pipeline was hacked in 2017. It shut down a large percentage of gas station gas purchases on the US East Coast.
There were lots of severe vulns since then: shellshock, log4j, the PHP vuln from a few weeks ago.
ps: wouldn't even be surprised if some of the banks hacks were related to this (branch) of exploit, given how much banks seem to rely on dated Java
That's what finally got Microsoft to get their act together with Windows.
1. May you live in interesting times
2. May you find what you're looking for
This too shall end.
https://en.wikipedia.org/wiki/This_too_shall_pass
"i hope you live forever"
The exploit conditions are very specific but there are still going to be a lot of hosts impacted. We at Semgrep published some free detection scripts here: https://github.com/semgrep/detection-scripts/tree/main/CVE-2...
They look for these five conditions:
Or, do running machines often have their CPU changed from under them without much notice?
I dunno about other cloud providers, but I know AWS can move your EC2 VM from one system to another transparently. There is a server ID you can get from the metadata, but unless you're checking it frequently, you can be moved without ever being aware.
In the case of transparent migration, I think it's basically a must. No JIT (or even libc probably) is going to support CPU features changing at runtime.
AWS migrates live instances to new CPUs without needing to stop or reboot the guest.
When a migration is needed, the hypervisor begins copying blocks of memory to the new system, keeping track of what blocks are written inside the guest during the migration. Once enough has been copied, it hibernates the guest, copies the remaining memory, then wakes it in the new system. On a system that isn't writing to large swaths of memory, it can take only a few milliseconds. To the guest, it might appear that the CPU froze for a tiny bit of time, which could easily just look like a neighbor got noisy.
Consider what would happen if you were live migrated from a machine with AVX512 to one without. Your app would suddenly start crashing with SIGILL for no apparent reason. So, live migrations always preserve the apparent CPU feature set. If you started on a machine without AVX512 then until the VM is rebooted you will remain on such a (virtual) machine.
Azul Platform Prime (formerly Zing) may or may not be depending on whether they touched the base64 intrinsic. Since it is closed-source there is no way to verify via code, which is how our research team investigates ecosystem events like this.
Here are three more, PTC, Aicas, and ART (even if it runs DEX instead, and only the core language is supported).
I've done Android development and there's nothing wrong with the way it's phrased. All of that is high signal information.
Thanks for the middlebrow dismissal
> According to Oracle, the following Oracle Java SE versions are vulnerable: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3. We thank Oracle for providing this information ahead of publication time.
So according to Oracle at least, JRE8 versions are affected as well.
[0] https://www.oracle.com/java/technologies/javase/jdk25-archiv...
[1] https://www.oracle.com/java/technologies/downloads/#java25
$FEATURE: increased every six months when new features are released (or removed) $INTERIM: currently always 0, reserved for future use $UPDATE: non-feature releases like bug, security or regression fixes. Releases one month after the feature version; then every three months $PATCH: important updates out of schedule
Specific implementations may introduce a fifth component for updates that do not come from the shared implementation but are distribution-specific (think Oracle fixing a bug that only happens in Oracle distributions)
(Then there's more, like +2 build numbers, and older versions have a slightly different format)
The circular financing continues!
But seriously, the funding here doesn't matter any more than Project Zero's funding comes from Google. Big companies are trying to improve security for the common software substrates of our industries / governments.
"improve security" in the same way that my dad used to beat us
-XX:-UseBASE64Intrinsics to disable hardware-accelerated Base64 encoding and decoding, or
-XX:UseAVX=2 to disable AVX-512. Apply this flag only on x86-64 hosts. OpenJDK on ARM doesn't recognize it and will fail to start.
I know I purposely do it for smolvm to avoid exposure
Or as it turns out an LLM! Not clear whether their agent spawned any classic tools...
I used memory protection for that. mmap a page, align the string start/end to the page boundaries. Catches both bad reads and writes.
Why do we even pay for Ubuntu?
https://www.debian.org/security/
Fortunately I run name-brand Oracle(R) Java(tm), which did publish updated packages.
I saw some assembly in code at work for various hot path stuff but it was all written before the last version control move. The 64-bit stuff was just done in plain C though which was probably good enough by the time it needed to updated to build as 64-bit.
Maybe distros could provide two builds, one for modern hardware only and one for maximum compatibility.
More annoying the first time you plug in that USB DAC or whatnot, but would reduce the attack surface heavily.
Who am I kidding... someone is going to comment that Dolphin Linux has supported this since 2013.
Before recently kernel security was relatively acceptable.
I started it in freebsd and later on Linux.
I'm not quite sure why I stopped the practice if I'm honest probably because generic felt good enough at some point and I forgot. Probably because my peripheral use became more chaotic.
That and most of the benefit is RAM footprint which stopped mattering.
See https://news.ycombinator.com/item?id=50371408
What makes it nasty is triggering it could be done so easily by url decoding, sending an email or many other things.
String operations also contain instrinsics.
Even your C standard library has assembly language implementations if things like strlen
Yes, JIT has lots of intrinsics.I had to inspect the crc32 loop (128bit vector instructions) as I expected to be faulty in some cases of unaligned data but it was fine.
I am very much aware where the assembly code for Hotspot is.
now panicking in case some LLM imported this without me noticing.
Genuinely curious, not meant to be a snarky or aggressive question.
Now it has lots of other little functions, like inline AES256 encryption/decryption and different functions names (like encode lines for b64 split over lines).
This is something I really like about LLVM. Their libc isn't spilling over with hand-written assembly. It's written in straightforward C++ under the belief that the compiler does, or will do, a good job.
Interestingly I remember a guy who worked on the JVM giving a talk and saying (back then at least) that they were working to move as much of the JVM to plain Java as they could.
> 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.
Mass exploitation, maybe. But LLMs are pretty good at finding exploits now as Calif showed at unprompted a few weeks ago.
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.
and the level of token require is not out of reach of many business either
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.
So, patch your systems, governments!
Don't see how this is a safe assumption in the modern era of LLMs.
LLMs aren’t magic, they can’t alter physics.
In particular booting a VM is cheap, having them in all potential regions won't break the bank.
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
Anyone mature enough not to write their own auth server? I agree with the sentiment.
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.
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.
https://www.cisa.gov/sites/default/files/2025-03/CSRBReviewO...
snort
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.
Haven't you heard of this new fangled thing called AI?
Some people love living under rocks.
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?
Our incredibly high tower of Jenga blocks is falling down under its own weight.
So many promotions because of optimizing cosmically unnecessary work, though.
Derp, derp, this is humans making computers.
As a person who does these kinds of optimizations, it hits in the feels.
http://move.rupy.se/file/base64.txt
If this part becomes the bottleneck; so I need to write a GPU accelerated version I'll eat my own hat.
I've easily reached a point where it was worth it to go AVX route in my "for funsies" game that I'm making.
I think only really smart people are going to be left in Security and Software. I can barely fathom what this group is doing with AI right now (ignoring that their model probably isn't nerfed) and I don't think any of this is trainable. This is starting to feel like some of the scientific fields where careers start when you get a MS/PhD. Or like the average developer now can't convert a Word document to PDF.
We'll see how long the centaur era lasts though. Hopefully a very long time
Once models are more hooked up to sources of information, their capabilities will improve. Currently, humans are a bottleneck for providing the information relative to specific problems.
"Take the human out of the loop" - I think there was a documentary about that, with Matthew Broderick.
I'm looking forward to eventually getting there. At the moment, there's so much low hanging fruit that even someone without a clue like me can just point a fuzzer at some random Linux kernel code and still discover problems.
(Most of the problems I found from that exercise are patched by now, if you use a recent enough kernel.)
I used Kimi to drive the fuzzer. The model didn't have to do anything smart, just do the tedious work of writing the glue code to make the fuzzing work. AFL++ did the 'smart' parts, and I had the idea to kick it off and oversaw the patches.
(for example, I have mine keep ready reference to all of our CMMC controls and best practices)- and not only will my sessions cite referenced material as it responds, but it will do so when it writes code, as well - and it does a pretty decent job of keeping me honest. The one bit I'm struggling with is limiting complexity when it designs a solution to a problem. For larger projects, this can snowball quickly - and I haven't found an effective way to prevent this yet.
Skills can be shared, but it's a bit of a steep climb to getting an entire organization to pick the same skill (to get consistent behavior across the whole org)- sometimes an individual skill as it's written, will conflict with some other personal standard or quirk of how they work, so it's difficult to share them. This really seems, to me, to be very similar to how the software world used to work (as far as interoperability goes), earlier in history when there weren't many open standards, (and NO open source code) - and every competing OS vendor was trying to destroy their competitors so they could become a monopoly.
But yes, there's quite a bit of effort now that goes into maintaining this personal harness, and I'm sure the even smarter folks will come along and figure out workable ways of standardizing and sharing those kinds of harnesses.
I've been in this industry for 30 years, and the way I work has always changed with the times and new tools. It changed a LOT when Dev Ops became a thing. IaC, and containers. This feels kind of like that change, but maybe an order of magnitude. Almost feels like going from assembler to learning something like python; in terms of how much abstraction is being added.
Could this be what triggered the recent outages?
https://x.com/InfiShark/status/2122786295105913332
But. Just. Why. Maybe just KISS.
When PHP2shell was announced, before the patches were available, I wrote a proxy to sanitize input. You should have an input-sanitizing proxy in front of your app servers anyway instead of waiting for patches for as-yet-undiscovered CVEs.
PHP < 8 doesn't have patches coming. It's either the proxy or be pwned. Some our honeypot machines running PHP 5 got infiltrated with full chained kernel-level exploits. The ones with the proxy didn't. Which one do you want to be?
https://github.com/Qbix/proxy -- now updated to help mitigate java4shell
Having said that, my proxy approach wouldn't fully protect ALL Java apps in this case, because:
A Java program that opens a TLS connection to a malicious server can be compromised, even if it exposes no service of its own.
The problem is that you can't intercept and "heal" TLS connections with a proxy, unless you also spoof the TLS certificates. However, since most Java apps don't pin certs, a workaround is using /etc/hosts and a CA cert added in cacerts. Then the proxy approach works even on outbound traffic. And you don't have to wait for the patches.
so what you'd do is: The usual disclaimers... lock down the executable, removing any ability to read or write files, only pass traffic through like a proxy. Investigate the repo yourself, with your own Claude or ChatGPT etc. The repo even has links to pre-fill the prompts to do just that.I'm putting this out under MIT license to help people, but under this license it disclaims all warranties, including implied warranty for merchantibility etc.
Anyone on a Debian derivative can use Ondřej Surý's packages which have the patch back ported to at least 7.3: https://deb.sury.org/
Also, I'm not sure I'd really trust what looks like LLM generated overly verbose code as a security layer.
Is it difficult to just go through Java, nodejs etc. Base64/hex/.. implementations and fuzz them all?
Does anyone know why this would be missed?
I am fairly sure it should still be possible to fuzz this by fuzzing the jit compiler. I understand it is not as easy as just fuzzing a regular function though.
It is even easier than fuzzing the JIT compiler in this case imo since it just inserts a fixed block of code which can be fuzzed seperately.
Well, at least we don't have any java server internet-facing here...
Source: https://github.com/adoptium/adoptium-support/issues/1575#iss...
Also, (S)FTP is dead? Since when?
Since it's overcomplicated ?
Should say "output_len & 0xFF >= 64" instead. Bzhi only looks at the bottom byte.
After checking, we discovered that they are using version 26, which is a non-lte version that hasn't received patches since March 2026, and also that our cluster runs on ARM64, which is not affected by the vulnerability.
https://openjdk.org/jeps/523
But there is part of article that somehow nobody mentions ! "A call for vibe-uncoding" and that is a future and sane sanity. How many unused Linux modules laying on disk ? And more commercial systems are usually worse - installer just unpacks and declares warranty void if something is modified or removed - law enforced stupidity.
You have [open] code ? You can clean it by doing very coarse work of not calling unused code or hardcoding return error on calling unused parts.
Like FTP code. Open source IT declared it dead years ago but camera and game manufacturers and probably more industries didn't get a memo. Still we do not implemented ftp replacement and ssh is single point of failure.
Their first priority is not stabilizing the tech tent. They are busy planning the risk distribution, risk outsourcing, legal prep, customer messaging, ToS/SLA reviews, contracts etc. They are reinforcing the good-old fort walls around the tech tent.
AI is... a horse?
It got a lot more popular recently when Cory Doctorow started talking about "reverse centaurs", where the job of the human is to assist the AI.
[1] https://medium.com/conversations-with-tyler/garry-kasparov-t...
I don't know, man. I just don't know.
All the (impressive!) distracting graphics, the speed of change, and the lack of commentary meant it took me a few watches to actually notice the ‘seashell’ segments were wrapping remote shells that the exploit had given them.
https://youtu.be/-EOYmL4UKvs