Forgot your password?
typodupeerror
Java AI Security The Internet

'Java4Shell' Flaw Exposes OpenJDK to RCE via Base64 (calif.io) 10

Longtime Slashdot reader HnT writes: Security researchers at Calif have disclosed Java4Shell (CVE-2026-114938), a critical 9.2-rated memory-corruption bug in OpenJDK's AVX-512 Base64 decoder. By sending a malformed string ending in a stray = character, attackers can trigger an out-of-bounds heap write to leak sensitive memory or achieve pre-auth remote code execution on major platforms like Jira, Jenkins, and Keycloak. Although Calif says the vulnerability is difficult to exploit, Oracle released a critical patch update Tuesday, and CISA urged organizations to update immediately. OpenJDK's security advisory can be found here.

The Calif researchers warned that vulnerable systems could remain exposed for five to 10 years, given how slowly some organizations patch their infrastructure.

'Java4Shell' Flaw Exposes OpenJDK to RCE via Base64

Comments Filter:
  • "memory-safe" (Score:2, Interesting)

    by Anonymous Coward

    Oops! Memory-safe except when you have handwritten SIMD code to accelerate base64 decoding.
    Well, glad it's getting fixed anyhow.

    • by DarkOx ( 621550 )

      I was going to say the same thing, but you beat me to it.

      Certainly beclowns one of the biggest arguments for Java.

      • And if you are running older x86_64 cpu's that lack some of the newer AVX512 instructions (ex avx512vbmi) your are supposedly safe.

      • by bsolar ( 1176767 )

        Certainly beclowns one of the biggest arguments for Java.

        The argument is not complete immunity from memory-safety issues, but a far reduced scope in which they are relevant and in which the developer needs to take care of them.

        There is no mainstream language that is 100% memory safe. All of them have at least some unsafe internals. The "memory safety guarantee" of the safe parts relies on the correctness of the unsafe internals they use.

        As example, from The Rustonomicon [rust-lang.org]:

        Much of the Rust standard library also uses Unsafe Rust internally. These implementations have generally been rigorously manually checked, so the Safe Rust interfaces built on top of these implementations can be assumed to be safe.

        That assumption holds only as long as those Unsafe Rust internal uses are actually bug-free, w

  • All I see is old hardware running Java 8.

    The future's so bright I gotta wear shades.

  • Is that like a fancy new compiler for Rust or Go? Never heard of it. /s

Nature, to be commanded, must be obeyed. -- Francis Bacon

Working...