Remix.run Logo
▲ pron a day ago

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.

▲ShinyLeftPad a day ago | parent [-]

Should jdk security team have wiped the PR then, if they noticed it? since it leaked a 0day

▲pron a day ago | parent [-]

Because it runs so much of the world's most important 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).

▲ a day ago | parent | next [-]
[deleted]
▲HappyDreamer a day ago | parent | prev [-]

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

▲pron a day ago | parent [-]

He's listed as the fix's co-author (and he's a friend; he's a regular contributor and a former Oracle employee).