Menu

Sixty-four A's and an equals sign break OpenJDK's Base64
📰

Sixty-four A's and an equals sign break OpenJDK's Base64

DEV Community·RC·about 15 hours ago
#Q477AYiW
#dev#array#openjdk#base64#calif
Reading 0:00
15s threshold

Sixty-four A characters and a trailing = are enough to write past the end of an array inside OpenJDK's Base64 decoder. Calif published the bug as Java4Shell (CVE-2026-114938) and scores it 9.2 under CVSS 4.0. On older OpenJDK 17 the trigger is 128 A s followed by = instead of 64.

The trigger string:

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

Enter fullscreen mode

Exit fullscreen mode

The decoder's fast path uses AVX-512 VBMI instructions on supported x86-64 processors to decode many bytes at once, and the bug lives in the hand-rolled assembly that handles the final characters. For that 65-byte input, OpenJDK allocates a 50-byte output array, decodes the first 64 characters cleanly, then mishandles the stray = and computes a negative output length. The negative length becomes a full 64-byte write, pushing 62 bytes past the end of the array. The runtime rejects the input a moment later, but by then neighboring heap objects may already be corrupted.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.