关联漏洞
描述
Scans for Log4j versions effected by CVE-2021-44228
介绍
[](https://www.inett.de/it-loesungen/checkmk)
# check_mk extension to check for log4j2 `CVE-2021-44228`
This Plugin wraps around
[logpresso/CVE-2021-44228-Scanner](https://github.com/logpresso/CVE-2021-44228-Scanner)
([Apache License 2.0](https://github.com/logpresso/CVE-2021-44228-Scanner/blob/main/LICENSE))
### [How it works](https://github.com/logpresso/CVE-2021-44228-Scanner#how-it-works)
Run in 5 steps:
1. Find all .jar, .war, .ear, .aar files recursively.
2. Find `META-INF/maven/org.apache.logging.log4j/log4j-core/pom.properties`
entry from JAR file.
3. Read groupId, artifactId, and version.
4. Compare log4j2 version and print vulnerable version.
文件快照
[4.0K] /data/pocs/3ea334dc309164e2bdc403e46dff7e7ec27e457a
├── [3.9K] Jenkinsfile
├── [ 15K] LICENSE
├── [4.0K] log4j-scanner
│ ├── [ 258] Dockerfile
│ ├── [4.7K] pom.xml
│ └── [4.0K] src
│ └── [4.0K] main
│ └── [4.0K] java
│ └── [4.0K] de
│ └── [4.0K] inett
│ └── [4.0K] cmk
│ └── [4.0K] log4shell
│ └── [2.2K] CliCheck.java
├── [4.0K] mkp
│ ├── [4.0K] agent_based
│ │ └── [2.9K] log4j_scanner.py
│ ├── [4.0K] build
│ │ ├── [ 243] mkp-pack
│ │ └── [ 337] update-version
│ ├── [ 179] Dockerfile
│ ├── [ 612] info
│ ├── [4.0K] lib
│ │ └── [4.0K] check_mk
│ │ └── [4.0K] base
│ │ └── [4.0K] cee
│ │ └── [4.0K] plugins
│ │ └── [4.0K] bakery
│ │ └── [ 755] log4j_scanner.py
│ └── [4.0K] web
│ └── [4.0K] plugins
│ └── [4.0K] wato
│ └── [1.9K] log4j_scanner.py
└── [ 739] README.md
20 directories, 13 files
备注
1. 建议优先通过来源进行访问。
2. 如果因为来源失效或无法访问，请发送邮箱到 f.jinxu#gmail.com 索取本地快照（把 # 换成 @）。
3. 神龙已为您对POC代码进行快照，为了长期维护，请考虑为本地POC付费，感谢您的支持。