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.
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).
Why invest more time to close it? The automation will do it for you.
In this case, there's evidence from a linked issue that Oracle was in communication with the author outside the PR. When you get a ping, and you know it's being worked on outside the PR, it does make sense to close it, cause you know it's being resolved elsewhere.
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.
> 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?
> 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.
The takeaway from this is not "the submitter was wrong", it's "we need to move off of openjdk yesterday".
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?
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.
I actually think the suggestion in the PR should have been auto accepted by an LLM.