This tool is to detect and fix the log4j log4shell vulnerability (CVE-2021-44228) by looking and removing the JndiLookup class from .jar/.war/.ear files with zero dependencies for free.
This tool has been tested on:
– Linux 32bit and 64 bit
– Windows 32 bit and 64 bit
– OpenBSD 64 bit
This tool is written in the Go programming language which means zero dependencies and standalone binaries which will run everywhere.
Download binaries (Windows, Linux, Darwin, OpenBSD) here https://github.com/nanitor/log4fix/releases/tag/v4.0.0
Scan file for vulnerability
./bin/log4fix detect </path/to/file.war>
Scan file for vulnerability and remove the vulnerable class.
./bin/log4fix fix </path/to/file.war> --overwrite
Scan directory for vulnerability.
./bin/log4fix scan </path/to/dir>
Scan directory for vulnerability and remove the vulnerable files. Note, this command overwrites the war/ear/jar files containing the vulnerable class that are found.
./bin/log4fix scan </path/to/dir> --fix
Scan directory for vulnerability and write the vulnerable jar/ear/war files found into the file supplied.
./bin/log4fix scan </path/to/dir> --output </path/to/text/file.txt>
We recommend taking a backup of the files prior to overwriting them.
On Windows, it may be necessary to stop the service prior to applying the fix.
Once the fix has been applied, the service should be restarted.
Build from source
This is functionally equivalent to the recommended remediation of
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
except it can also go into other .jar/.war/.ear files and look for
log4j-core-*.jar file in there and
removing the JndiLookup class from there.
And of course works on all platforms.