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

reply
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?

reply
At the time maybe he assumed it was just a crash.
reply
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.

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

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