Ok i have found this: https://github.com/hillu/local-log4j-vuln-scanner/releases
The binary can be renamed as a .sh script and run local on a workstation and works great for vulnerable log4j jar file detection.
I want to be able to utilize this with an extension attribute and a smart group to see what machines have vulnerable log4j jars.
Can anyone provide details on how to make this happen?
