News for hackers. Stuff that matters.
Re:Someone reported java4shell bug in September 2026 by black3r on Thursday November 19, 2026 @11:20AM (#50562104)
The very first referenced issue in that PR discussion sheds a bit more light on this: https://github.com/adoptium/adoptium-support/issues/1480

This PR's author says there on October 1st: "Got an email from Oracle asking me to NOT proceed with a PR until receiving approval." and then on October 28th: "It's taken over by Oracle. Nothing required from us."

Re:Someone reported java4shell bug in September 2026 by mzs on Thursday November 19, 2026 @11:41AM (#50562434)
should have known at this point it's a potential security issue and maybe the AI regurgitated this:

https://github.com/adoptium/adoptium-support/issues/1480#iss...

Re:Someone reported java4shell bug in September 2026 by pixl97 on Thursday November 19, 2026 @01:27PM (#50564023)
The proper way to deal with a security bug in any Oracle software is to zero day it.

They are the biggest asshole of a company when it comes to anything, but especially security issues. They are one of the least friendly companies to security researchers and are likely to attack you with lawyers.

Fuck Oracle. We should be putting them out of business.

Re:Someone reported java4shell bug in September 2026 by malfist on Thursday November 19, 2026 @01:48PM (#50564374)
This is called throwing the baby out with the bathwater.
Re:Someone reported java4shell bug in September 2026 by pixl97 on Thursday November 19, 2026 @02:22PM (#50564931)
No, not really. This baby is rotten and infected with a corporate culture that looks to extract as much money out of you via any way possible, especially lawfare. If you're standing up with Oracle I need to point at the sign again.

The sign: "Do not fall into the trap of anthropomorphizing Larry Ellison. Think of Larry Ellison the way you think of a lawn mower. You don't anthropomorphize your lawn mower. Your lawn mower just mows the lawn. You stick your hand in there, it'll chop it off, the end. You don't think "oh the lawn hates me!" the lawn mower doesn't give a shit about you. Your lawn mower can't hate you. Don't anthropomorphize the lawn mower. Don't fall into that trap about Oracle."

Re:Someone reported java4shell bug in September 2026 by RIMR on Thursday November 19, 2026 @02:34PM (#50565088)
I really struggle to understand why anyone would trust a company that started as a CIA domestic surveillance project. The government's tentacles are deeply embedded in this company, which is partly why they feel so emboldened to engage in lawfare against anyone who might challenge them.
Re:Someone reported java4shell bug in September 2026 by strictnein on Thursday November 19, 2026 @10:09PM (#50569682)
[delayed]
Re:Someone reported java4shell bug in September 2026 by vips7L on Thursday November 19, 2026 @05:23PM (#50567319)
I’ve been using Java for 15 years and Oracle has never gotten a cent from me. YMMV though.
Re:Someone reported java4shell bug in September 2026 by KingOfCoders on Friday November 20, 2026 @12:14AM (#50570448)
You paying money is just one wrong click by any employee away. Then the Oracle Global Licensing and Advisory Services is on you with an audit. And then you hire a consultant from the Oracle license consultant industry to help you through.
Re:Someone reported java4shell bug in September 2026 by vips7L on Friday November 20, 2026 @05:57AM (#50572964)
No it’s not.
Re:Someone reported java4shell bug in September 2026 by KingOfCoders on Friday November 20, 2026 @07:07AM (#50573595)
Hi Larry.
Re:Someone reported java4shell bug in September 2026 by easterncalculus on Thursday November 19, 2026 @02:39PM (#50565166)
There is no baby. This is throwing out the squatter in your basement.
Re:Someone reported java4shell bug in September 2026 by malfist on Thursday November 19, 2026 @03:43PM (#50566081)
I'm sure all the people compromised by a zeroday in java think they're a squatter in your basement.
Re:Someone reported java4shell bug in September 2026 by tejtm on Thursday November 19, 2026 @02:42PM (#50565202)
sometimes Darwin solutions are the best solutions
Re:Someone reported java4shell bug in September 2026 by pixl97 on Thursday November 19, 2026 @03:03PM (#50565528)
Yesterday on a post I was stating that Responsible Disclosure has been the worst thing for computing ever. It has lulled humanity into the idea that computers are safe and we've built just massive amounts of digital infrastructure under that delusion.

If every bug was a zero day then we'd have never hooked things like water grids and electrical grids to networks. Grocery stores and bloodbanks would have never put freezers on the internet. Along with a million other huge security risks, too many to be named here.

The AI age has exposed that stupidity.

Re:Someone reported java4shell bug in September 2026 by malfist on Thursday November 19, 2026 @03:06PM (#50565590)
That's just not true. People don't hook up freezers to the internet because they think it's safe, they do it because it's cheap and convenient, and saves having to send someone out to manually check them every X hours. The free market doesn't reward more than legally minimum safety requirements.
Re:Someone reported java4shell bug in September 2026 by josnyder on Thursday November 19, 2026 @03:42PM (#50566069)
Your view can be harmonized with your parent comment's view.

Capitalism rewards all sorts of safety requirements, if they become visible to a balance sheet within a reasonable period of time. Just look at marine insurance in the middle east right now.

The status quo is that IoT freezers are massively inconvenient every decade or so. Businesses can live out an entire lifecycle in this period of time, without the risk ever hitting their balance sheet.

pixl97 is saying: what if we made the risk far more common, so that its effect shows up on a balance sheet within 6-12 months?

Re:Someone reported java4shell bug in September 2026 by smuhakg on Thursday November 19, 2026 @09:35PM (#50569476)
> pixl97 is saying: what if we made the risk far more common, so that its effect shows up on a balance sheet within 6-12 months?

What is the purpose of this? It's just intentionally making hacks more common and a net negative for the economy.

More secure systems aren't inherently good. You don't hear people talking about how happy they are that break-ins are common and everyone locks their doors before leaving the house.

Re:Someone reported java4shell bug in September 2026 by pixl97 on Thursday November 19, 2026 @09:54PM (#50569587)
>More secure systems aren't inherently good.

I'm sorry buddy, but you were born in the wrong universe not to defend yourself.

The internet is a global network. This means people not under your sovereign jurisdiction can reach out and fuck with your data and you can do jack shit about it unless you want to take a bunch of other really expensive actions (for example economic or hot warfare).

Computer people should know better than thinking that the internet is anything other than an inherently hostile place. Groups we consider enemy nations share the same web space. Countries that make $1000 a year share the same web space, and all the juicy servers you leave insecure look like a very good way for them to become absolutely rich. Hell, even people in your own country are apt to get away with hacking with a little bit of skill.

The internet is not your neighborhood. You can't call the police to fix every little issue for you. It is a literal war zone, just most people are still in denial about that.

Now start treating it like that.

Re:Someone reported java4shell bug in September 2026 by po1nt on Thursday November 19, 2026 @05:13PM (#50567211)
Because of the daddy state safety net, people are not risk aware. If they suffer the consequences they can always push for more state control in the spirit of "why did you let me do this". Whole prohibition stood on this idea.
Re:Someone reported java4shell bug in September 2026 by malfist on Thursday November 19, 2026 @10:09PM (#50569681)
What a ridiculous assertion. Do you go around sticking every small object in your mouth just because it doesn't have a sticker about chocking hazards?
Re:Someone reported java4shell bug in September 2026 by jodrellblank on Friday November 20, 2026 @09:02AM (#50574791)
The two most common causes of child death in the USA are parents running over their own children in their cars, and guns.

Please feel free to explain how people are not aware of the danger of running over their own children because of the daddy state, and how fun owners have somehow missed the dangers of guns.

The consequences are usually suffered by other people. You speed, other people die in the resulting crash. You get the freedom to make unsafe buildings and furniture and electrical goods for profit, other people die from them collapsing and burning down.

Re:Someone reported java4shell bug in September 2026 by hobo123 on Friday November 20, 2026 @12:39AM (#50570581)
You know VPNs exist, right? Nobody has to hook their devices/freezers into the OPEN Internet.
Re:Someone reported java4shell bug in September 2026 by happymellon on Friday November 20, 2026 @07:18AM (#50573690)
Hell, what about the raspberry pi that logs all the temperatures and forwards them to the central supermarket logging system.

Why is there not a proxy so we don't need to expose the refrigerators to even a VPN?

Re:Someone reported java4shell bug in September 2026 by somenameforme on Friday November 20, 2026 @03:05AM (#50571573)
I don't think this is the issue. Freezers are extremely reliable. They're built to operate 24 hours a day for years on end. They're also designed to maintain approximate temperature (when full) for about 2 days, so even a freak outage isn't that big a deal.

There's no real problem being solved. People just went that direction to follow trend of 'smart' everything because it's cheap, you can concoct hypothetical scenarios where it might be useful (regardless of whether or not they're at all realistic), and most importantly of all - complete lack of awareness about the risks involved.

Re:Someone reported java4shell bug in September 2026 by mschuster91 on Friday November 20, 2026 @05:06AM (#50572546)
> There's no real problem being solved.

There actually is. Humans are notoriously sloppy in following mundane, boring compliance bullshit tasks, and noting down freezer temperatures is what I'd say very high up on the list of bullshit tasks that are so pointless they're demeaning to the human who has to be the eyes for the machine.

Connecting the freezers to a central logging facility now needs no human checking the freezer every hour and writing down the temperature on a sheet of paper no one will ever read. It is precisely what machines are made for. And since compliance is now automatic instead of a strong incentive for the human to just invent "valid" data and be done, actual outages can now be spotted much faster.

Re:Someone reported java4shell bug in September 2026 by somenameforme on Friday November 20, 2026 @07:12AM (#50573637)
Again for normal usage this is not a very realistic scenario. Freezers generally keep relatively near to their target temperatures, when full, for about 48 hours. A grocery store or something might have it as part of a routine maintenance schedule alongside bathrooms, trash bins, etc but this is hardly some problem that needs solving, especially not if one is aware of the risks.
Re:Someone reported java4shell bug in September 2026 by RobotToaster on Friday November 20, 2026 @03:18AM (#50571679)
> People don't hook up freezers to the internet because they think it's safe

I don't think that's true.

They may have known there was a risk, but historically it was small. If they knew it was certain to be hacked before next Thursday most would stop doing it pretty quickly.

It's like driving. Every time you drive there's a small chance of an accident, but everyone still does it. If there was a 50% chance of death most would stop doing it pretty quickly.

Re:Someone reported java4shell bug in September 2026 by aftbit on Thursday November 19, 2026 @06:02PM (#50567796)
Securely networking electrical grids offers improvements in reliability, which translates directly to safety. If the power goes off on a hot summer afternoon, people die. Networking enables faults to be detected and resolved faster, reducing the amount of time that the system stays in dangerous conditions.

Similarly, (securely) networking water treatment plants enables people to remotely verify that settings are where they're supposed to be and adjust them to match changing sample reports or intake conditions, reducing the risk of over-treating or under-treating the water, both of which can have safety consequences.

On top of that, networking enables much greater efficiency. Rather than having a person sitting at every substation ready to throw a breaker, or more likely, ready to drive there (taking time), you can have them sitting in a control room that monitors the whole grid at once.

Much of modern life would be much more expensive and much less safe without networking.

We really shouldn't throw the baby out with the bathwater. It is possible to build secure systems. It takes a certain degree of paranoia and dedication that humans find difficult, and a willingness and ability to respond quickly to unknown threats, but that doesn't make it impossible.

Re:Someone reported java4shell bug in September 2026 by pixl97 on Thursday November 19, 2026 @06:13PM (#50567910)
>Much of modern life would be much more expensive and much less safe without networking.

The modern world wouldn't work without gasoline, but it's burning the planet to the ground in the meantime.

If your efficiency is gained by taking the brakes off the car to make it lighter you're going to realize how bad you screwed up when it comes time to stop.

We've been playing a 30 year game of fucking around and we're reached find out time.

If we want to build secure systems we're going to have to flush about 95% of the programmers out there.

Re:Someone reported java4shell bug in September 2026 by aftbit on Thursday November 19, 2026 @07:35PM (#50568619)
On the other hand, we wouldn't have gotten to fiber and 5G without spending some time on copper wires first.

I agree about one thing - incentives cannot work properly if it takes you 30 years to find out but your economy is built on 3 month business cycles.

We don't need to flush 95% of the programmers (though that is probably happening anyway). We need to flush 95% of the incentives to go fast and avoid spending money. Fast, cheap, or good - if you're very lucky and very good, you can squeeze two of them out of the equation. Most of the time, you're lucky to get even one.

Re:Someone reported java4shell bug in September 2026 by pron on Thursday November 19, 2026 @08:14PM (#50568926)
We did know it was a potential security risk, and that is why it was handled exactly how security-sensitive issues are supposed to be handled (not to mention that the reporter is a well-respected OpenJDK contributor and former Oracle colleague).

I don't know if people here understand how these things need to be done in the most important and critical open source projects, such as Linux or OpenJDK, but there are two things you must not do when an issue is suspected to be a risk until you've researched the matter and decided on a backport and release strategy: You shouldn't communicate publicly, and you absolutely shouldn't merge a patch.

Re:Someone reported java4shell bug in September 2026 by bawolff on Thursday November 19, 2026 @09:09PM (#50569297)
Well i understand where this view comes from, sometimes it can feel like its a net negative for security in the end.

Full disclosure might cause short term panic, but it does get things fixed quickly.

Re:Someone reported java4shell bug in September 2026 by pron on Thursday November 19, 2026 @09:46PM (#50569530)
When your product runs the world, you need to coordinate exactly how a patch is released across multiple versions and when, and you don't want to tip your hand before everything is ready. A lot is riding on doing this right.
Re:Someone reported java4shell bug in September 2026 by guiambros on Thursday November 19, 2026 @09:59PM (#50569620)
[delayed]
Re:Someone reported java4shell bug in September 2026 by aljgz on Thursday November 19, 2026 @11:08PM (#50570042)
This still does not change how security critical bugs should be handled. It's expected that ability to run models follows a power law distribution: very few actors are able to run the most expensive models on many codebases/binaries.

Disclosing a serious vulnerability potentially exposes it to orders of magnitude more people.

Re:Someone reported java4shell bug in September 2026 by bostik on Friday November 20, 2026 @12:28AM (#50570520)
There is case to be made that with the LLM-powered vulnerability research any bug found with the help of an LLM should be considered public.

If I spent N tokens to find a specific funky bug, you should expect others to have done the same. In a way, in this modern age the full-disclosure guys had it right all along. Reality caught up with a three decade lag.

Re:Someone reported java4shell bug in September 2026 by hobo123 on Friday November 20, 2026 @12:37AM (#50570565)
Also, for something that you could just deactivate, it's absolutely unacceptable for Oracle to take so long. Deactivating the intrinsic would have been a few-line patch that they could have easily ported to all branches and then communicated to other vendors. Shouldn't have taken more than 2 days to fix.

Shit like this is what forces people to just _merge_ fixes, why shouldn't they?

Re:Someone reported java4shell bug in September 2026 by pron on Friday November 20, 2026 @09:00AM (#50574773)
That would be irresponsible. A vulnerability isn't closed once you merge a fix, and not once you release builds. It's closed when users apply the patch in production. That takes time no matter how quickly you release, and could come at the expense of other things your users may want to do, including addressing other vulnerabilities. Turning a bug into an exploit can also take time, even with the help of AI.

So until you know how dangerous the bug is and have a plan for release (does it go in the next quarterly patch, which users are ready for, or are you making a special release?) you shouldn't do anything public because you don't yet know what to advise your users to do.

Re:Someone reported java4shell bug in September 2026 by znpy on Thursday November 19, 2026 @05:44PM (#50567585)
I’m usually a java supporter because i have fond memories of working with it and great experiences from working with high throughput/low latency stuff written in java… HOWEVER: I’ll frame that comment as a smoking gun the next time somebody says java is fully independent from oracle (btw this used to also be me, but i clearly have to change my position)
Re:Someone reported java4shell bug in September 2026 by aftbit on Thursday November 19, 2026 @06:03PM (#50567811)
Java fully independent from Oracle? Who would think that? The OpenJDK is mostly paid for by Oracle and Red Hat. Control always follows money.