News for hackers. Stuff that matters.
Re:Someone reported java4shell bug in September 2026 by wood_spirit on Thursday November 19, 2026 @10:10AM (#50561134)
So the implication is that the LLM that assisted the Calif researchers might have read this previous bug report and not independently discovered it?
Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @10:44AM (#50561608)
Idk that u/notmine1337 meant that. I have questions:

- why was this not a secure vulnerability report, why was it public?

- why was this closed [by the submitter]?

Re:Someone reported java4shell bug in September 2026 by jakewins on Thursday November 19, 2026 @11:10AM (#50561963)
Why it was closed, surely, was because the only reaction to the PR was a bot saying it will automatically close the PR soon because of inactivity?

I know I have opened a lot of PRs where the only result is I get bot spam in my email and no project reaction, so I close the PR to stop the bot spam; if nobody from Oracle has reacted in 2 months it seems unlikely anyone will.

Nowadays I’ve stopped opening “cold-call” PRs like this. I find a way to chat with a maintainer first and anchor what I want to do (“I hit this bug, would you take a PR to fix it? I was thinking it could be solved by x, would that work?”

Much much better outcomes that way.

Re:Someone reported java4shell bug in September 2026 by eru on Thursday November 19, 2026 @01:17PM (#50563830)
Though in the age of LLM, I really wonder what the benefit of asking for permission to make a PR is? It's not like you are wasting much effort, if they don't want it. And if they do want it, the PR is right there, instead of waiting for another round-trip.
Re:Someone reported java4shell bug in September 2026 by ApolloFortyNine on Thursday November 19, 2026 @01:50PM (#50564411)
Yea I've let claude make a couple PRs when it's clearly a bug in the repo, if the maintainer wants to take a stand against AI PRs so be it, my local copy has the fix.
Re:Someone reported java4shell bug in September 2026 by ajasmin on Thursday November 19, 2026 @02:40PM (#50565178)
There may still be an incline to give the PR’s fix strategy a “fair chance” and feel obliged to comb through it, which if the changes is somewhat intricate can present a bigger hump to get through.
Re:Someone reported java4shell bug in September 2026 by philipwhiuk on Thursday November 19, 2026 @11:13AM (#50561995)
> why was this not a secure vulnerability report, why was it public?

Because it was seen as a crash not an RCE. AI's power has been chaining simple crashes into exploits. But that's not generally going to be true.

Re:Someone reported java4shell bug in September 2026 by wat10000 on Thursday November 19, 2026 @11:25AM (#50562166)
I'd be surprised if that's what happened. The instant I see "corrupting the heap" I assume it's a serious vulnerability unless proven otherwise. AI is taking it to another level, but the days of dismissing memory corruption as unexploitable died years before.
Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @12:49PM (#50563409)
100% this.
Re:Someone reported java4shell bug in September 2026 by eru on Thursday November 19, 2026 @01:18PM (#50563849)
Yes, even before LLMs it was a common heuristic that if you can make something crash, with a bit more cleverness you can usually take over.
Re:Someone reported java4shell bug in September 2026 by pron on Thursday November 19, 2026 @03:44PM (#50566090)
That is precisely why it wasn't dismissed and why there were no public comments on this PR.
Re:Someone reported java4shell bug in September 2026 by dlenski on Thursday November 19, 2026 @11:21AM (#50562115)
I don't think that's a reasonable implication at all.

There are lots of bugs in lots of software, and lots of them get ignored when reported.

I personally aware of multiple security vulnerabilities in major pieces of software that everyone has heard of, which I very quickly and easily stumbled on while working on this software as an AWS engineer several years ago. I had never used an LLM of any kind at the time.

I presented my findings both internally and externally, and the reactions ranged from shrugs to delays to hostility towards me for "getting distracted" or "being overly negative."

Those bugs that I discovered still exist, last time I checked.

Re:Someone reported java4shell bug in September 2026 by ajasmin on Thursday November 19, 2026 @02:32PM (#50565059)
Minimum Secure Product -> Ship it to prod.
Re:Someone reported java4shell bug in September 2026 by larodi on Thursday November 19, 2026 @04:43PM (#50566857)
> I don't think that's a reasonable implication at all.

the contrary is very likely thing the agent may have done, given they... like agents dig the web, don't they. and if im a security researcher digging through Oracle's shit, the open issues sure does look a good starting point.

Re:Someone reported java4shell bug in September 2026 by dannyw on Friday November 20, 2026 @08:10AM (#50574190)
Professional security researchers don’t run these kind of models with unrestricted Internet access.

You don’t want the tail risk of explaining how your agent did an E2E RCE of GitHub.com and exfil’d several $BIGCORP’s private repositories.