You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+9-7
Original file line number
Diff line number
Diff line change
@@ -3,28 +3,30 @@
3
3
log4j2-scan is a single binary command-line tool for CVE-2021-44228 vulnerability scanning and mitigation patch. It also supports nested JAR file scanning and patch.
If you add `--fix` option, this program will copy vulnerable original JAR file to .bak file, and create new JAR file without `org/apache/logging/log4j/core/lookup/JndiLookup.class` entry. In most environments, JNDI lookup feature will not be used. However, you must use this option at your own risk. It is necessary to shutdown any running JVM process before applying patch. Start affected JVM process after fix.
27
27
28
+
If you want to automate patch job, use `--force-fix` option. With this option, this program will no longer prompt for confirmation.
29
+
28
30
`(mitigated)` tag will be displayed if `org/apache/logging/log4j/core/lookup/JndiLookup.class` entry is removed from JAR file.
29
31
30
32
If you add `--trace` option, this program will print all visited directories and files. Use this option only for debugging.
@@ -49,7 +51,7 @@ Completed in 0.42 seconds
49
51
50
52
### How it works
51
53
Run in 5 steps:
52
-
1. Find all .jar files recursively.
54
+
1. Find all .jar, .war, .ear files recursively.
53
55
2. Find `META-INF/maven/org.apache.logging.log4j/log4j-core/pom.properties` entry from JAR file.
54
56
3. Read groupId, artifactId, and version.
55
57
4. Compare log4j2 version and print vulnerable version.
0 commit comments