Summaries
Short AI and tech summaries with source links, signal scores, and why each update matters for builders, founders, and Malaysian tech workers.
Showing 1-1 of 1 results
| Date | Provider | Score | Summary |
|---|---|---|---|
| 19 Nov 2026, 7:47 PM | Hacker News | 6.5 | Someone reported java4shell bug in September 2026
OpenJDK PR #32781 (by albertnetymk, opened Sep 9 2026, now closed) describes a heap-corrupting bug in the x86_64 AVX-512 VBMI Base64 decode intrinsic: in StubGenerator::generate_base64_decodeBlock(), the L_finalBit path computes output_size = (len/4)*3, and for a leftover tail under 4 bytes the padding path decrements it below zero, producing a wrong output_mask so the stub writes past the logical output length before returning to Java. It only triggers on invalid input — the write-up's example is "A".repeat(64)+"=", which leaves 1 byte after L_process64Loop — since valid Base64 is always a multiple of 4. The proposed fix is a one-line early return to Java when length < 4; the HN thread drew 307 points and 82 comments, and the PR text itself does not name a CVE, a severity, or the 'java4shell' label used in the submission title. Why: If you run JVM services on AVX-512 VBMI hardware (Ice Lake / Sapphire Rapids / Zen 4-class x86_64) and decode attacker-supplied Base64, this is a case where malformed input causes memory corruption instead of a clean IllegalArgumentException — so length validation on your side (`s.length() % 4 == 0`) is worth adding in front of java.util.Base64 rather than trusting the decoder to fail safely. The PR is marked Closed, not merged, so don't assume a shipped JDK contains the fix: check your build's changelog before treating this as patched. The other concrete detail is the 'OpenJDK Interim AI Policy' confirmation line in the PR body — a signal that AI-assisted contributions to core JDK intrinsics are now arriving with their own review conventions. |