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
[ Parent
| on HN ]
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?)