Particle.news

Critical Java4Shell Flaw in OpenJDK Base64 Decoder Prompts Patch and Active Scanning

Crafted Base64 input can corrupt the JVM heap to disclose secrets or enable remote code execution, prompting urgent patches.

Overview

  • Calif disclosed the vulnerability Tuesday and said researcher Quang Luong used AI tools to find a memory‑corruption bug in OpenJDK’s AVX‑512 hardware‑accelerated Base64 decoder.
  • Oracle and the OpenJDK project released fixes on November 17 and downstream vendors are publishing patched builds, but full remediation requires replacing running JVM binaries and restarting every Java process.
  • The flaw affects OpenJDK builds from 17.0.6 onward when they run on x86‑64 CPUs that report AVX‑512 VBMI support and does not impact ARM64 or non‑AVX‑512 hosts.
  • Researchers demonstrated pre‑authentication remote code execution against default installations of Keycloak, Jira, Confluence, Jenkins, Artifactory and PingFederate, and threat intelligence firms reported scanning and probe attempts on November 18–19 without confirmed large‑scale intrusions.
  • Short‑term mitigations include JVM startup flags (-XX:-UseBASE64Intrinsics or -XX:UseAVX=2), isolating internet‑facing identity and build systems, and hunting for pre‑patch compromises because successful exploits need target‑specific heap grooming and address leaks even though AI sped development.