News for hackers. Stuff that matters.
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.