Some applications bundle their own Java runtime, so a normal JDK inventory may miss them. How do you find those copies, prioritize fixes, and explain the remaining exposure to management?
How are you finding Java4Shell exposure and deciding what to patch first?
Answers
Start with your software inventory or vulnerability scanner to find the obvious installations, but treat that as a starting list. Check application directories for bundled runtimes, review container images and running containers, and ask appliance vendors which Java builds they ship.
Record the runtime version and vendor alongside the application and host. A patched host does not mean the Java runtime inside a container or application bundle is patched. Some of those will need an application or vendor update rather than a standalone JDK update.
Reply to this answer
Use the runtime and CPU together to narrow the list. The reported issue involves an OpenJDK Base64 code path using AVX-512 VBMI. On Linux, uname -m shows the architecture and grep -m1 -o 'avx512vbmi' /proc/cpuinfo checks whether that flag is exposed.
ARM systems and x86-64 systems without the flag are not known to be affected by that code path. Check what the virtual machine sees, since a physical host's features don't necessarily tell you what's exposed to the guest. Keep the result with the Java version and check current vendor guidance before closing an item.
Reply to this answer
I'd put exposed services with an affected, unpatched runtime and the relevant CPU feature at the front of the queue. Then work through internal systems and anything still awaiting confirmation.
Oracle having a patch doesn't mean every bundled runtime has an update yet. Track vendor availability separately and use vendor-recommended workarounds where a fix isn't available. Don't let assumptions about how difficult exploitation might be replace that triage.
Reply to this answer
For management, keep it simple: how many systems are confirmed affected, how many are still being checked, what has been patched, and which fixes depend on a vendor. Call out any workarounds and when the next status update will be available.
_k53!fendrix.7:
Separating confirmed exposure from systems still under investigation should make the numbers easier to explain.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Zavmelo-4q:
Running java -version inside a live container can help identify its runtime. Also check the images used for new deployments, not just containers running now.