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