enoqlooking at the latest java4shell vulnerability, there are no eclipse temurin docker images available yet, correct?
enoqwhat version does 25.0.5_8 correspond to?
enoqI suppose 25.0.5+8 which is not 25.0.5.1
jbosmansit's pretty fresh so i think the images and temurin itself still needs to be updated. For vuln systems I'd look into the mitigations to switch from avx512 to avx2 support
ParaAdd -XX:-UseBASE64Intrinsics to your JVM opts by whatever mechanism works for your case, redeploy, onwards to next CVE.
ParaSpecifically this requires the AVX-512 VBMI instruction which is quite rare in reality, rough estimate is that only about 15-20% of CPUs out there even have it, and it's entirely possible cloud service providers haven't enabled it in hypervisor settings anyway, so the attack surface to mitigate is very confusing.
[twisti]'quite rare' ... '20%'
[twisti]well i certainly relaxed, probably wont even bother to look into it
ParaThat 20% includes AMD Zen4 and Zen5 processors, which are mostly home user CPUs.
enoqthank you
sonOfRaI've switched a bunch of systems to - XX:UseAVX=2 instead of wholly disabling intrinsics. With java -XX:+PrintFlagsFinal -version, you can quickly find out if the system you're on supports avx512- there will be a UseAVX value of 3 in the output somewhere. If it says 2, or nothing at all, at least that particular jvm on your system is unaffected
enoqsonOfRa: so you expect there to be more avx issues?
sonOfRaNo, it's a tradroff. My workload in this case is keycloak and due to the whole jwt deal it does a lot of base64 - so disabling base64 acceleration probably loses me more than falling back to avx2 for everything
sonOfRaI'll see in my cpu metrics after a day or two. Performance might even improve, because avx512 is not always actually a speedup due to silly cpu architecture reasons
deeboyeah was just about to ask what minor version does temurins 25.0.5+8 correspond to, is it still vulnerable?
nevetETA for Temurin 25 and 21 releases fixing CVE-2026-114938 (Base64 intrinsic memory corruption, "Java4Shell") · Issue #1575 · adoptium/adoptium-support
sonOfRaenoq: first 2 hours of production workload show no statistically significant performance deviation from our 30 day mean after setting useavx=2
sonOfRaYMMV
ParaIt's also somewhat framework dependent if you even hit the native base64 path. Run something old/backwards compatible enough and it uses e.g. Commons Codec instead.
deeboalso requires 4 cpu features to be available, those are reserved for slop agents, not to run real software!
enoqhad a look at some claude generated java code recently btw
enoqloads of while and for loops with break and continue statements
enoqrefactoring took as long as implementing the feature from scratch
dreamrealenoq: that sounds like whoever was driving did a poor job
deeboyeah needs more handholding for style, or a checker tool that says no
deeboshould finally setup spotless and some static analyzer
deebosonarqube was a lifesaver until they decided they wont support java>8 in the "free" version
cheeserdeebo: spotless is great. i have it autowired in to my build cycles.
dreamrealI do too
dreamrealcheeser: what happened to javabot? Should I unmute nevet?
sonOfRapmd+spotless as a pre-commit hook works wonders to rein in claude
Optici just checked all our physical servers against the cpu capabilities required for java4shell, and we don't own a single one with avx512 :P
Opticwe have a couple with bmi2
Opticsometimes shit old hardware is a win??
dreamrealall of our deployed servers are technically vulnerable but don't expose endpoints that would provide easy ingress. So naturally we're sure we're invulnerable! *sigh* (We're deploying with the flag even so. "invulnerable" is a descriptor that only means "we don't know the ingress yet.")
Optici'm going to wait for the November patch cycle to release and calmly deploy that everywhere
dreamrealWe just deployed new images with the flags in place
dreamrealcoretto images are already patched but they're 120+ MB larger than temurin and we don't rely on the base64 decoding enough for it to impact us negatively
Opticall our stuff is in spring-boot containers, so when liberica pubs the new versions it will just be a CI trigger + deploy to update
ParaJust in time for the next CVE, nested KVMs.
Zapekwhere did oracle hide the graalvm with the base64 fix...
dreamrealright there behind the paywall!
ParaHm, I should probably slap pmd+spotless+whatever else into my template repo.
cheeserdreamreal: restarting it now
dreamrealcheeser: I tried to start it yesterday but it was apparently unsuccessful
deeboproper enterprise java is on java8 and thus invulnerable
* dreamreal snrks
ParaAnd definitely not on x86 derivatives.
Para(that's too new)
Para((my Hetzner VM is protected because its CPU is ancient and doesn't support any AVX))
dreamrealcheeser: what happened when I tried to start it?
nimajedeebo: but at least some java8 versions are vulnerable, oracle says oracle java se 8u511b33-perf is vulnerable. No idea if any other as well, or why they just call out that specific version, is that just their currently supported java8 version? Does anyone else still support some java8 version?
cheeserdreamreal: i didn't see anything about that.
dreamreal*nod* I started it and waiting for a few minutes and it never showed up here, didn't do any triage
sbalmosdreamreal: maybe it's like Python where if you're missing something, it just silently does nothing on startup. :D