Skip to content

Commit 1a39e19

Browse files
committed
Updated version to 1.2.4
1 parent c991752 commit 1a39e19

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@
33
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.
44

55
### Download
6-
* [log4j2-scan 1.2.3 (Windows x64)](https://github.com/logpresso/CVE-2021-44228-Scanner/releases/download/v1.2.3/logpresso-log4j2-scan-1.2.3-win64.7z)
7-
* [log4j2-scan 1.2.3 (Linux x64)](https://github.com/logpresso/CVE-2021-44228-Scanner/releases/download/v1.2.3/logpresso-log4j2-scan-1.2.3-linux.tar.gz)
8-
* [log4j2-scan 1.2.3 (Any OS, 10KB)](https://github.com/logpresso/CVE-2021-44228-Scanner/releases/download/v1.2.3/logpresso-log4j2-scan-1.2.3.jar)
6+
* [log4j2-scan 1.2.4 (Windows x64)](https://github.com/logpresso/CVE-2021-44228-Scanner/releases/download/v1.2.4/logpresso-log4j2-scan-1.2.4-win64.7z)
7+
* [log4j2-scan 1.2.4 (Linux x64)](https://github.com/logpresso/CVE-2021-44228-Scanner/releases/download/v1.2.4/logpresso-log4j2-scan-1.2.4-linux.tar.gz)
8+
* [log4j2-scan 1.2.4 (Any OS, 10KB)](https://github.com/logpresso/CVE-2021-44228-Scanner/releases/download/v1.2.4/logpresso-log4j2-scan-1.2.4.jar)
99

1010
### How to use
1111
Just run log4j2-scan.exe or log4j2-scan with target directory path.
@@ -20,7 +20,7 @@ On Linux
2020
```
2121
On UNIX (AIX, Solaris, and so on)
2222
```
23-
java -jar logpresso-log4j2-scan-1.2.3.jar [--fix] [--trace] target_path
23+
java -jar logpresso-log4j2-scan-1.2.4.jar [--fix] [--trace] target_path
2424
```
2525

2626
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.

0 commit comments

Comments
 (0)