{"uuid": "8b336dc8-f4da-4f79-b095-d687b5375184", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-44228", "type": "seen", "source": "https://t.me/hacking_Attack/35598", "content": "KitPloit - PenTest Tools!\nLog4J-Detector - Detects Log4J versions on your file-system within any application that are vulnerable to CVE-2021-44228 and CVE-2021-45046\n\nhttp://1.bp.blogspot.com/-l4ckIu8tvZw/YcAH6RuFLZI/AAAAAAAA5s8/-Q23DmKD8RoDI7CKAFMU9O2VVL1j5-ncgCK4BGAYYCw/w640-h150/log4j-detector_1_log4j-detector-778008.png Detects Log4J versions on your file-system within any application that are vulnerable to CVE-2021-44228  and CVE-2021-45046. It is able to even find instances that are hidden several layers deep. Works on Linux, Windows, and Mac, and everywhere else Java runs, too!\n\nCurrently reports log4j-coreversions 2.12.2 and 2.17.0 as _SAFE_, 2.15.0 and 2.16.0 as _OKAY_ and all other versions as _VULNERABLE_  (although it does report pre-2.0-beta9 as \"_POTENTIALLY_SAFE_\").\n\nCan correctly detect log4j inside executable spring-boot jars/wars, dependencies blended  into uber jars, shaded jars, and even  exploded jar files just sitting uncompressed on the file-system (aka *.class).\n\nWe currently maintain a collection of log4j-samples we use for testing. Example Usage:java -jar log4j-detector-2021.12.17.jar [path-to-scan] > hits.txt http://1.bp.blogspot.com/-l4ckIu8tvZw/YcAH6RuFLZI/AAAAAAAA5s8/-Q23DmKD8RoDI7CKAFMU9O2VVL1j5-ncgCK4BGAYYCw/w640-h150/log4j-detector_1_log4j-detector-778008.png More Example Usage:java -jar log4j-detector-2021.12.17.jar ./samples \n\n-- github.com/mergebase/log4j-detector v2021.12.17 (by mergebase.com) analyzing paths (could take a while).\n-- Note: specify the '--verbose' flag to have every file examined printed to STDERR.\n/opt/mergebase/log4j-detector/samples/clt-1.0-SNAPSHOT.jar contains Log4J-2.x   >= 2.10.0 _VULNERABLE_ :-(\n/opt/mergebase/log4j-detector/samples/infinispan-embedded-query-8.2.12.Final.jar contains Log4J-2.x   >= 2.0-beta9 (< 2.10.0) _VULNERABLE_ :-(\n/opt/mergebase/log4j-detector/samples/log4j-1.1.3.jar contains Log4J-1.x <=\n/opt/mergebase/log4j-detector/samples/log4j-1.2.13.jar contains Log4J-1.x <=\n/opt/mergebase/log4j-detector/samples/log4j-1.2.17.jar contains Log4J-1.x <=\n/opt/mergebase/log4j-de   tector/samples/log4j-core-2.0-beta2.jar contains Log4J-2.x <=\n/opt/mergebase/log4j-detector/samples/log4j-core-2.0-beta9.jar contains Log4J-2.x   >= 2.0-beta9 (< 2.10.0) _VULNERABLE_ :-(\n/opt/mergebase/log4j-detector/samples/log4j-core-2.0.2.jar contains Log4J-2.x   >= 2.0-beta9 (< 2.10.0) _VULNERABLE_ :-(\n/opt/mergebase/log4j-detector/samples/log4j-core-2.0.jar contains Log4J-2.x   >= 2.0-beta9 (< 2.10.0) _VULNERABLE_ :-(\n/opt/mergebase/log4j-detector/samples/log4j-core-2.10.0.jar contains Log4J-2.x   >= 2.10.0 _VULNERABLE_ :-(\n/opt/mergebase/log4j-detector/samples/log4j-core-2.12.2.jar contains Log4J-2.x   >= 2.12.2 _SAFE_ :-)\n/opt/mergebase/log4j-detector/samples/log4j-core-2.14.1.jar contains Log4J-2.x   >= 2.10.0 _VULNERABLE_ :-(\n/opt/mergebase/log4j-detector/samples/log4j-core-2.15.0.jar contains Log4J-2.x   >= 2.15.0 _OKAY_ :-|\n/op   t/mergebase/log4j-detector/samples/log4j-core-2.16.0.jar contains Log4J-2.x   >= 2.16.0 _OKAY_ :-)\n/opt/mergebase/log4j-detector/samples/log4j-core-2.17.0.jar contains Log4J-2.x   >= 2.16.0 _SAFE_ :-)\n/opt/mergebase/log4j-detector/samples/log4j-core-2.4.1.jar contains Log4J-2.x   >= 2.0-beta9 (< 2.10.0) _VULNERABLE_ :-(\n/opt/mergebase/log4j-detector/samples/log4j-core-2.9.1.jar contains Log4J-2.x   >= 2.0-beta9 (< 2.10.0) _VULNERABLE_ :-( Understanding The Results_VULNERABLE_ -> You need to upgrade or remove this file.\n\n_OKAY_ -> We only report this for Log4J versions 2.15.0 and 2.16.0. We recommend upgrading to 2.17.0.\n\n_SAFE_ -> We currently only report this for Log4J versions 2.17.0 and 2.12.2.\n\n_OLD_ -> You are safe from CVE-2021-44228, but should plan to upgrade because Log4J 1.2.x has been EOL for 7 years and has several known-v[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:02.971616Z"}