News for hackers. Stuff that matters.
Re:Someone reported java4shell bug in September 2026 by InsidiousWombat on Thursday November 19, 2026 @10:17AM (#50561212)
Nice proof that the auto-close bots are literal cancer on project that make stuff worse.

It was literal bug with provided fix. All it needed is someone to have a proper look.

But someone clowned a bot under a visionary thought "if nobody looked it must not be important" and here we are

Re:Someone reported java4shell bug in September 2026 by stickfigure on Thursday November 19, 2026 @10:28AM (#50561378)
Agreed, but in this case it looks like the submitter closed it? What's that about?
Re:Someone reported java4shell bug in September 2026 by dboreham on Thursday November 19, 2026 @10:39AM (#50561527)
They knew about the fix coming?
Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @10:46AM (#50561634)
That's my guess. But also opening a public issue was a faux pas.
Re:Someone reported java4shell bug in September 2026 by philipwhiuk on Thursday November 19, 2026 @11:14AM (#50562011)
At the time maybe he assumed it was just a crash.
Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @12:47PM (#50563390)
From the report:

> The stub stores past the logical output length before returning to Java, corrupting the heap.

It was obviously a security vulnerability. That the project didn't immediately re-write then close the PR and admonish submitter is astounding.

Re:Someone reported java4shell bug in September 2026 by dpkirchner on Thursday November 19, 2026 @01:43PM (#50564303)
Given they (those best able to understand the significance of the crash) didn't consider the bug worth fixing, I'm not sure why they'd admonish the submitter. Or why submitters in the future should act more carefully.

The takeaway from this is not "the submitter was wrong", it's "we need to move off of openjdk yesterday".

Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @03:32PM (#50565945)
Assumes facts not in evidence. We do not know that the maintainers "didn't consider the bug worth fixing". And yes, submitters should "act more carefully" when they know they are reporting a vulnerability.
Re:Someone reported java4shell bug in September 2026 by dpkirchner on Thursday November 19, 2026 @05:11PM (#50567181)
The segfault was reported several months ago (see https://news.ycombinator.com/item?id=50562104). If the submitter went through project zero we'd be well past the 90 day window. How is that not sufficient evidence?
Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @10:55PM (#50569951)
> The segfault was reported several months ago (see https://news.ycombinator.com/item?id=50562104).

Did OpenJDK fix the bug only when Java4shell came out, or did they have a fix in progress? Gemini and Claude tell me the fix had already been in the works. Therefore your earlier:

> > > Given they (those best able to understand the significance of the crash) didn't consider the bug worth fixing,

is false, and indeed that was 'facts not in evidence'.

> If the submitter went through project zero we'd be well past the 90 day window. How is that not sufficient evidence?

There is no evidence of "they [...] didn't consider the bug worth fixing". On the contrary, there is evidence that they did consider it worth fixing.

Re:Someone reported java4shell bug in September 2026 by dlenski on Thursday November 19, 2026 @11:25AM (#50562182)
> But also opening a public issue was a faux pas.

Sorry, but why?

Why should someone discovering a bug in an enormously complex piece of software have any responsibility for assessing the security implications of that bug?

If the maintainers wanted to make it private they could have done so.

Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @12:48PM (#50563400)
Submitter wrote:

> The stub stores past the logical output length before returning to Java, corrupting the heap.

That's obviously a security vulnerability. If they didn't understand that, how did they even find it?

Re:Someone reported java4shell bug in September 2026 by pimterry on Thursday November 19, 2026 @11:24AM (#50562152)
They closed themselves immediately after the stale bot pinged to say it was going to be closed automatically. If you're not that investigated in a PR for a niche corruption bug, you open it and nobody responds for two months, when you get notified about it it's pretty reasonable to just close and move on. Perfectly normal OSS contributor behaviour imo (especially in this new world where every project is drowning under AI contributions, and struggling to stay responsive).
Re:Someone reported java4shell bug in September 2026 by toast0 on Thursday November 19, 2026 @11:35AM (#50562354)
> you open it and nobody responds for two months, when you get notified about it it's pretty reasonable to just close and move on.

Why invest more time to close it? The automation will do it for you.

Re:Someone reported java4shell bug in September 2026 by eviks on Thursday November 19, 2026 @12:59PM (#50563536)
For example, not to get another useless notification from a bot later
Re:Someone reported java4shell bug in September 2026 by bombcar on Thursday November 19, 2026 @10:30AM (#50561402)
Grab a billion tokens and farm auto-closed GitHub issues. Become HN famous for a day.
Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @10:30AM (#50561407)
It wasn't auto-closed.
Re:Someone reported java4shell bug in September 2026 by lol768 on Thursday November 19, 2026 @02:15PM (#50564810)
Doesn't matter, it was about to be.
Re:Someone reported java4shell bug in September 2026 by cryptonector on Thursday November 19, 2026 @04:07PM (#50566378)
We don't know that.

If I were the relevant maintainer I would have reached out to submitter privately and asked them to hold off more widely reporting this, and I would not have stopped the bot from announcing impending closure.

Re:Someone reported java4shell bug in September 2026 by dboreham on Thursday November 19, 2026 @10:38AM (#50561520)
A project with auto bug close signals to me that it is badly managed and hence should be used with caution.
Re:Someone reported java4shell bug in September 2026 by lol768 on Thursday November 19, 2026 @02:16PM (#50564821)
Completely agree with this. At some point I want to make a side-project that you can run that auto-comments on tickets to keep them alive.
Re:Someone reported java4shell bug in September 2026 by frangonf on Thursday November 19, 2026 @10:39AM (#50561538)
Even Duke gave up on the current state of software.

Would it be better to have some Oracle gpus running the dukebot? Are the robobun and friends better at real triage/escalation? Could we automate the robobots to register the `java2root.com` domain on its own, release a blog post and post it in twitter/hn upon every successful security issue?

Re:Someone reported java4shell bug in September 2026 by wat10000 on Thursday November 19, 2026 @11:22AM (#50562130)
The bot auto-closes issues that have been inactive for 16 weeks. The CVE was published at about 10 weeks in. The auto-close bot was completely irrelevant to this. The issue wasn't that it got auto-closed (it didn't) but that nobody from the project looked at the PR. That's a hard problem to solve, because any big project has a lot of volume and it's easy to miss things. It's unfortunate but a fact of life that you can't just toss up a PR and expect anyone to automatically look at it.
Re:Someone reported java4shell bug in September 2026 by fn-mote on Thursday November 19, 2026 @11:38AM (#50562393)
> you can't just toss up a PR and expect anyone to automatically look at it.

Except soon you can expect LLM triage to be standard.

We would then find out if enough tokens would be invested in this one to figure out it was important, but any look is better than none.

Re:Someone reported java4shell bug in September 2026 by pron on Thursday November 19, 2026 @02:00PM (#50564594)
I work on the JDK, and while I have no involvement with this issue, knowing how we work, what has likely happened is quite the opposite. Bugs don't slip through our triage, and every bug that leads to a VM crash, especially in the compiler backend, is flagged for security review by the security research team; once that happens, no public communication is done. I don't know this is what happened here, but it is the most likely thing to have happened.

We're not talking any large open source project here. We're talking about a project that, like Linux, runs much of the world's software infrastructure, and even bugs that could potentially be vulnerabilities need to be handled with great care.

Re:Someone reported java4shell bug in September 2026 by ShinyLeftPad on Thursday November 19, 2026 @02:45PM (#50565251)
Should jdk security team have wiped the PR then, if they noticed it? since it leaked a 0day
Re:Someone reported java4shell bug in September 2026 by pron on Thursday November 19, 2026 @03:13PM (#50565679)
Because it runs so much of the world's software, the JDK is heavily watched, and removing a PR would only draw attention to it.

Also, it's not really a leaked 0-day because there's ways to go from a bug to an exploit (even going from Calif's detailed public report to an exploit is not trivial, because exploits depend on the particular application; there has been no disclosed exploit that requires only the JDK).

Re:Someone reported java4shell bug in September 2026 by fweimer on Thursday November 19, 2026 @03:28PM (#50565900)
The associated Jira ticket is private, though: https://bugs.openjdk.org/browse/JDK-8392044

Isn't there an expectation that non-security PRs refer to a public ticket? As a result, a private ticket is a pretty strong signal.

Re:Someone reported java4shell bug in September 2026 by HappyDreamer on Thursday November 19, 2026 @05:58PM (#50567757)
Thanks for explaining!

I'm guessing Oracle won't get back to the person later and say "thanks now fixed was actually a high sev vuln" (I can understand if everyone is short of time and can't keep track of such things?)

Re:Someone reported java4shell bug in September 2026 by pron on Thursday November 19, 2026 @08:07PM (#50568875)
He's listed as the fix's co-author (and he's a friend; he's a regular contributor and a former Oracle employee).