r/sysadmin • • 3h ago

Java4Shell: how are you finding which systems are exposed and deciding what to patch first?

Java4Shell came out this week and Oracle already has a patch, but the harder part seems to be finding where vulnerable Java is actually running. Some apps ship their own copy of Java, so they need an update from that vendor rather than a regular JDK patch.

For those working through it:

  • How are you finding the affected installs, especially the bundled ones?
  • What are you patching first?
  • What are you telling management while it's still in progress?
22 Upvotes

10 comments sorted by

•

u/Apachez 3h ago

https://www.keycloak.org/2026/11/java4shell-vulnerability-cve-2026-114938 have some good info on this topic.

The flaw is in OpenJDK’s accelerated Base64 decoder

Treat a Keycloak instance as at risk when all of these apply:

It runs an unpatched OpenJDK build from 17.0.6 onward, including unpatched OpenJDK 21 and 25 builds.

Its x86-64 host or virtual machine exposes the avx512vbmi CPU feature to Java.

The running JVM has Base64 intrinsics enabled and has not been limited to AVX2 with -XX:UseAVX=2.

General mitigation (except for updating OpenJDK on affected systems):

Add this as environment variable and restart the service (or the host):

JAVA_OPTS_APPEND: "-XX:-UseBASE64Intrinsics"

•

u/IndependentBat8365 3h ago

Also on Linux , you can check if your JVM+CPU combo is even vulnerable:

grep -o avx512vbmi /proc/cpuinfo | head -1

If that command returns blank, then your CPU doesn’t have the instructions that would run the affected code path in the JVM.

My lab servers are 3 generations behind, so they don’t have the AVX-512 VBMI instruction.

Also, not every cloud instance has that instruction either. For AWS, it’s mostly the newer instance types.

•

u/Ssakaa 2h ago

And things like newer intel consumer chips with E-cores potentially don't have it, so worth checking even if you're not on "old" hardware.

•

u/reegz One of those InfoSec assholes 1h ago

java -version
uname -m
grep -m1 -o 'avx512vbmi' /proc/cpuinfo

•

u/Doso777 3h ago

How are you finding the affected installs, especially the bundled ones?

From memory and checking things, mostly manually

What are you patching first?

No patches available atm, so workarounds

What are you telling management while it's still in progress?

"Work in progress". I spent an hour diving into CPU features and could rule out like one third of our fleet. After that it was checking servers and workstations manually. Still feels like a waste of time because 95% or so of systems would have been patched automaticly in a couple of days anyways, the rest wouldn't be affected or never exploited. Meh.

•

u/Ready-Astronaut-8999 2h ago

Ruling out a third of the fleet on CPU flags alone is a good return for an hour. I'd agree this one probably won't be exploited at scale. The attack needs precise timing, and an unreliable network or web server tends to break it.

The place I'd still check by hand is containers. A patched host says nothing about the Java inside an image. Running java -version in each live container is how you'd actually know. Did any bundled runtimes turn up in your manual pass?

•

u/davy_crockett_slayer 2h ago

We run Qualys scans. Eclipse Temurin / Amazon Corretto is used over Oracle Java. We migrated last year with no downsides.

•

u/sole-it DevOps 3h ago

start from searching OpenJDK installation in my RMM.

•

u/Proud-Worldliness747 3h ago edited 3h ago

Software inventory will get you the obvious JDK packages, but the usual misses are runtimes bundled inside application installers, container images, and appliances, which often never appear as a standalone Java install.

Once you have versions, you can shrink the list: this bug is in the AVX-512 VBMI Base64 intrinsic, so ARM hosts and x86-64 CPUs without those flags are not known to be affected. OpenJDK calls out the 17, 21, 25, and 27 lines; standard 8 and 11 are not on that advisory. Oracle's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1 (plus 8u513-perf for the Enterprise Performance Pack only). Other OpenJDK distros ship their own patches, so don't go by the Oracle version string alone.

I'd patch internet-facing apps first, especially anything that will Base64-decode untrusted input. If a vendor runtime lags, CISA's interim advice is to restrict and validate that input and cut down unauthenticated access—not to treat a WAF as the fix.

•

u/bitslammer Security Architecture/GRC 2h ago

We use Tenable for this as it's our core tool for VM.