How are you finding bundled Java runtimes on Windows and appliances?

November 19, 2026 5 answers
Asked by 8m~ferrulebadge_417

With Java4Shell exposure in mind, what's a practical way to inventory JREs bundled inside vendor applications? I'm looking at Windows systems and appliances, where installed software lists may not tell the whole story.

Answers

_p73~zavquelo.6

Start with a file search across Windows endpoints, not just the installed programs list. A bundled runtime can sit inside a vendor application's directory without showing up as a separate Java installation.

A quick PowerShell pass is Get-ChildItem -Path C:\ -Recurse -Filter java.exe -ErrorAction SilentlyContinue. Record the full path for each result, then look for a release file in the runtime directory and check its version. The release file may be above the bin folder containing java.exe, rather than beside the executable.

This is a starting inventory, not a guarantee that you've found every runtime. Suppressed errors can hide inaccessible directories, and searching one drive and one filename has obvious gaps.

q.283+pluvano:

Also check javaw.exe where it makes sense. Keep the application path in the report so you can trace each runtime back to its owner.

Reply to this answer
_w57!tavreno.3

If Defender for Endpoint is already deployed, try its software inventory and advanced hunting before sending a recursive scan everywhere. Search for Java executable filenames and look at the paths associated with vendor apps. You can also filter the vulnerability view for the CVE as another lead.

Don't treat an empty vulnerability result as proof that every bundled runtime is accounted for. Compare the results with file or process data and investigate gaps in coverage.

Reply to this answer
v.492~zeldruno

Process monitoring is useful for narrowing down which machines are actually launching Java. An endpoint management tool or SIEM may have records for java.exe, javaw.exe, or jre.exe, along with the executable path.

That only catches what ran during the period you can see, though. A dormant bundled runtime won't necessarily appear in launch logs, so I wouldn't use this as the sole inventory.

Reply to this answer
_c89+fendavo.2

For appliances, go straight to the vendor's advisory for the specific product and version. You may not have access to scan the underlying filesystem, and the vendor needs to tell you whether its appliance is affected and what update or mitigation applies.

8m~ferrulebadge_417:

That makes sense. I'll track appliance versions alongside the vendor responses rather than assume a Windows inventory covers them.

Reply to this answer
_e95~vorteli.2

If you already use SCCM, a configuration baseline and report can give you a repeatable way to collect Java version information across endpoints. Check what the baseline actually detects, especially runtimes bundled under application directories, rather than assuming the report includes them.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions