
Scanner di vulnerabilità e patch di mitigazione per Log4j2 CVE-2021-44228

log4j2-scan è uno strumento da riga di comando a binario singolo per la scansione della vulnerabilità CVE-2021-44228 e l'applicazione della patch di mitigazione. Supporta inoltre la scansione e la patch di file JAR annidati. Rileva anche CVE-2021-45046 (log4j 2.15.0), CVE-2021-45105 (log4j 2.16.0), CVE-2021-44832 (log4j 2.17.0), CVE-2021-4104, CVE-2019-17571, CVE-2017-5645, CVE-2020-9488, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307 (log4j 1.x) e CVE-2021-42550 (logback 0.9-1.2.7).
Puoi integrare log4j2-scan con il servizio Logpresso Watch per la reportistica e la gestione delle patch. Visita https://logpresso.watch per i dettagli.
VCRUNTIME140.dll not found, installa Visual C++ Redistributable.Esegui semplicemente log4j2-scan.exe o log4j2-scan con il percorso della directory di destinazione. logpresso-log4j2-scan.jar dovrebbe funzionare con JRE/JDK 7+
L'opzione --fix è supportata per le seguenti vulnerabilità:
L'opzione --fix non mitiga le seguenti vulnerabilità:
Utilizzo
Logpresso CVE-2021-44228 Vulnerability Scanner 3.0.1 (2022-02-13)
Usage: log4j2-scan [--scan-log4j1] [--fix] target_path1 target_path2
-f [config_file_path]
Specify config file path which contains scan target paths.
Paths should be separated by new line. Prepend # for comment.
--scan-log4j1
Enables scanning for log4j 1 versions.
--scan-logback
Enables scanning for logback CVE-2021-42550.
--scan-zip
Scan also .zip extension files. This option may slow down scanning.
--zip-charset
Specify an alternate zip encoding other than utf-8. System default charset is used if not specified.
--fix
Backup original file and remove JndiLookup.class from JAR recursively.
With --scan-log4j1 option, it also removes JMSAppender.class, SocketServer.class, SMTPAppender.class, SMTPAppender$1.class,
JMSSink.class, JDBCAppender.class, and all classes of org.apache.log4j.chainsaw package
--force-fix
Do not prompt confirmation. Don't use this option unless you know what you are doing.
--restore [backup_file_path]
Unfix JAR files using zip archived file.
--backup-path [zip_output_path]
Specify backup file path.
--backup-ext [zip]
Specify backup file extension. zip by default.
If --backup-path is specified, this option is ignored.
--all-drives
Scan all drives on Windows
--drives c,d
Scan specified drives on Windows. Spaces are not allowed here.
--no-symlink
Do not detect symlink as vulnerable file.
--exclude [path_prefix]
Path prefixes of directories whose absolute path starts with the specified value will be excluded.
Does not support relative paths. You can specify multiple --exclude [path_prefix] pairs
--exclude-config [config_file_path]
Specify exclude path prefix list in text file. Paths should be separated by new line. Prepend # for comment.
--exclude-pattern [pattern]
Exclude specified paths of directories by pattern. Supports fragments.
You can specify multiple --exclude-pattern [pattern] pairs (non regex)
--exclude-file-config [config_file_path]
Specify exclude file path list in text file. Paths should be separated by new line. Prepend # for comment.
--exclude-fs nfs,tmpfs
Exclude paths by file system type. nfs, nfs3, nfs4, afs, cifs, autofs,
tmpfs, devtmpfs, fuse.sshfs, smbfs and iso9660 is ignored by default.
--api-key [key]
Send reports to Logpresso Watch service.
--http-proxy [addr:port]
Send reports via specified HTTP proxy server.
--syslog-udp [host:port]
Send reports to remote syslog host.
Send vulnerable, potentially vulnerable, and mitigated reports by default.
--syslog-level [level]
Send reports only if report is higher or equal to specified level.
Specify alert for vulnerable and potentially vulnerable reports.
Specify info for vulnerable, potentially vulnerable, and mitigated reports.
Specify debug for vulnerable, potentially vulnerable, mitigated, and error reports.
--syslog-facility [code]
Default value is 16 (LOCAL0). Facility value must be in the range of 0 to 23 inclusive.
--rfc5424
Follow RFC5424 The Syslog Protocol strictly.
--report-csv
Generate log4j2_scan_report_yyyyMMdd_HHmmss.csv in working directory if not specified otherwise via --report-path [path]
--report-json
Generate log4j2_scan_report_yyyyMMdd_HHmmss.json in working directory if not specified otherwise via --report-path [path]
--report-patch
Report also patched log4j file.
--report-path
Specify report output path including filename. Implies --report-csv.
--report-dir
Specify report output directory. Implies --report-csv.
--no-empty-report
Do not generate empty report.
--csv-log-path
Specify csv log file path. If log file exists, log will be appended.
--json-log-path
Specify json log file path. If log file exists, log will be appended.
--old-exit-code
Return sum of vulnerable and potentially vulnerable files as exit code.
--debug
Print exception stacktrace for debugging.
--trace
Print all directories and files while scanning.
--silent
Do not print progress message.
--throttle
Limit scan files per second.
--help
Print this help.
Su Windows
log4j2-scan [--fix] target_path
Su Linux
./log4j2-scan [--fix] target_path
Su UNIX (AIX, Solaris, ecc.)
java -jar logpresso-log4j2-scan-3.0.1.jar [--fix] target_path
Se aggiungi l'opzione --fix, questo programma copierà il file JAR originale vulnerabile in un file .bak e creerà un nuovo file JAR senza la voce org/apache/logging/log4j/core/lookup/JndiLookup.class. Tutti i file .bak vengono archiviati in un unico file zip chiamato log4j2_scan_backup_yyyyMMdd_HHmmss.zip, quindi eliminati in modo sicuro. Nella maggior parte degli ambienti, la funzionalità di lookup JNDI non viene utilizzata. Tuttavia, devi usare questa opzione a tuo rischio. Puoi facilmente ripristinare i file JAR originali vulnerabili usando l'opzione --restore.
A seconda del sistema operativo:
Se vuoi automatizzare il lavoro di patch, usa l'opzione --force-fix. Con questa opzione, il programma non richiederà più conferma.
Il tag (mitigated) verrà visualizzato se la voce org/apache/logging/log4j/core/lookup/JndiLookup.class viene rimossa dal file JAR.
Se aggiungi l'opzione --trace, questo programma stamperà tutte le directory e i file visitati. Usa questa opzione solo per il debug.
Su Windows:
CMD> log4j2-scan.exe D:\tmp
[*] Found CVE-2021-44228 vulnerability in D:\tmp\elasticsearch-7.16.0\bin\elasticsearch-sql-cli-7.16.0.jar, log4j 2.11.1
[*] Found CVE-2021-44228 vulnerability in D:\tmp\elasticsearch-7.16.0\lib\log4j-core-2.11.1.jar, log4j 2.11.1
[*] Found CVE-2021-44228 vulnerability in D:\tmp\flink-1.14.0\lib\log4j-core-2.14.1.jar, log4j 2.14.1
[*] Found CVE-2021-44228 vulnerability in D:\tmp\logstash-7.16.0\logstash-core\lib\jars\log4j-core-2.14.0.jar, log4j 2.14.0
[*] Found CVE-2021-44228 vulnerability in D:\tmp\logstash-7.16.0\vendor\bundle\jruby\2.5.0\gems\logstash-input-tcp-6.2.1-java\vendor\jar-dependencies\org\logstash\inputs\logstash-input-tcp\6.2.1\logstash-input-tcp-6.2.1.jar, log4j 2.9.1
[*] Found CVE-2021-44228 vulnerability in D:\tmp\solr-7.7.3\solr-7.7.3\contrib\prometheus-exporter\lib\log4j-core-2.11.0.jar, log4j 2.11.0
[*] Found CVE-2021-44228 vulnerability in D:\tmp\solr-7.7.3\solr-7.7.3\server\lib\ext\log4j-core-2.11.0.jar, log4j 2.11.0
[*] Found CVE-2021-44228 vulnerability in D:\tmp\solr-8.11.0\contrib\prometheus-exporter\lib\log4j-core-2.14.1.jar, log4j 2.14.1
[*] Found CVE-2021-44228 vulnerability in D:\tmp\solr-8.11.0\server\lib\ext\log4j-core-2.14.1.jar, log4j 2.14.1
Scanned 5047 directories and 26251 files
Found 9 vulnerable files
Completed in 0.42 seconds
Viene eseguito in 5 passaggi:
META-INF/maven/org.apache.logging.log4j/log4j-core/pom.properties dal file JAR.log4j2_scan_backup_yyyyMMdd_HHmmss.zip, quindi elimina i file .bak.Se hai domande o problemi, crea una issue in questo repository.
Logpresso è un'azienda leader nel settore dell'IA e dei big data con sede in Corea del Sud. Logpresso fornisce soluzioni SIEM, SOAR, gestione dei log e FDS con la propria piattaforma big data.