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