Java4Shell: disable JVM Base64 intrinsics until the VM is patched
Original title: Java4Shell is a reason to use Java
The author ties the flaw to a handwritten assembly Base64 intrinsic and gives -XX:-UseBASE64Intrinsics as a temporary flag.
Ethan McCue describes Java4Shell, less than a day old when he wrote, as a problem in how the Java Virtual Machine intrinsifies Base64 encoding. He tells operators of unpatched Java deployments to add -XX:-UseBASE64Intrinsics and later upgrade to a patched VM. He argues the issue is widespread because it sits in shared native JVM code, while ordinary Java remains memory safe and native library access can be restricted. The post gives no CVE, patched build or confirmed attacks.
Unconfirmed: Impact, affected builds and whether attackers are exploiting Java4Shell are not stated.
- The suggested temporary flag is -XX:-UseBASE64Intrinsics.
- The author says the flaw comes from a handwritten assembly intrinsic.
- Native access can become a hard error unless a library is explicitly enabled.
- No patched JVM version is named.
| Product | Affected |
|---|---|
| Java Virtual Machine | — |
- 1.Add -XX:-UseBASE64Intrinsics to unpatched Java VM flags.
- 2.Upgrade the VM to a patched version when one is available.
From the original article
2 min read at mccue.devWe're less than a day into dealing with "Java4Shell" , an issue stemming from how the Java Virtual Machine intrinsifies Base64 encoding code. If you have a Java deployment you haven't updated yet, add -XX:-UseBASE64Intrinsics to the VM flags. Then upgrade your VM to a version where the issue is patched when you can.
By mccue.dev by emccue · mccue.dev
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.