{"uuid": "09ad9972-e499-4342-b7ae-14d0385d5d23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-45046", "type": "seen", "source": "https://t.me/hacking_Attack/35594", "content": "/opt/mergebase/log4j-detector/samples/log4j-core-2.9.1.jar contains Log4J-2.x   >= 2.0-beta9 (< 2.10.0) _VULNERABLE_ :-(\n  Understanding The Results  _VULNERABLE_ -> You need to upgrade or remove this file.  _OKAY_ -> We only report this for Log4J versions 2.15.0 and 2.16.0. We recommend upgrading to 2.17.0.  _SAFE_ -> We currently only report this for Log4J versions 2.17.0 and 2.12.2.  _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-vulnerabilities.  _POTENTIALLY_SAFE_ -> The \"JndiLookup.class\" file is not present, either because your version of Log4J is very old (pre 2.0-beta9), or because someone already removed this file. Make sure it was someone in your team or company that removed \"JndiLookup.class\" if that's the case, because attackers have been known to remove this file themselves to prevent additional competing attackers from gaining access to compromised systems.  This Scanner Only Reports Hits Against The log4j-core Library. What About log4j-api?  Many scanners (including GitHub's own Dependabot (https://github.com/dependabot)) currently report both \"log4j-core\" and \"log4j-api\" libraries as vulnerable.  These scanners are incorrect. There is currently no existing version of the \"log4j-api\" library that can be exploited by any of these vulnerabilities.  Why Report About 2.10.0, 2.15.0, 2.16.0, and 2.17.0 ?  We consider version 2.10.0 important because that's the first version where Log4J's vulnerable \"message lookup feature\" can be disabled via Log4J configuration.  We consider versions 2.15.0 and 2.16.0 important because these are the first versions where Log4J's default out-of-the-box configuration is not vulnerable to CVE-2021-44228.  And version 2.17.0 is important because it's not vulnerable to CVE-2021-45046. Despite CVE-2021-45046 being much less serious,  we anticipate everyone will want to patch to 2.17.0.  What are those \"file1.war!/path/to/file2.zip!/path/to/file3.jar!/path/to/log4j.jar\" results about?  The \"!\" means the log4j-detector entered a zip archive (e.g., *.zip, *.ear, *.war, *.aar, *.jar). Since zip files can  contain zip files, a single result might contain more than one \"!\" indicator in its result.  Note:  the log4j-detector only recursively enters zip archives. It does not enter tar or gz or bz2, etc. The main reason  being that Java systems are often configured to execute jars inside jars, but they are never configured to execute other  file formats (that I know of!). And so a log4j copy inside a *.tar.gz is probably not reachable for a running Java  system, and hence, not a vulnerability (https://www.kitploit.com/search/label/Vulnerability) worth reporting.  2nd note:  for zips-inside-zips our scanner does load the inner-zip completely into memory (using ByteArrayInputStream)  before attempting to scan it. You might need to give Java some extra memory if you have extremely large inner-zips on  your system (e.g., 1 GB or larger).  Usage  detector (version 2021.12.17)  Docs  - https://github.com/mergebase/log4j-detector   (C) Copyright 2021 Mergebase Software Inc. Licensed to you via GPLv3.\">java -jar log4j-detector-2021.12.17.jar \n\nUsage: java -jar log4j-detector-2021.12.17.jar [--verbose] [paths to scan...]\n\nExit codes:  0 = No vulnerable Log4J versions found.\n             1 = At least one legacy Log4J 1.x version found.\n             2 = At least one vulnerable Log4J version found.\n\nAbout - MergeBase log4j detector (version 2021.12.17)\nDocs  - https://github.com/mergebase/log4j-detector \n(C) Copyright 2021 Mergebase Software Inc. Licensed to you via GPLv3.\n  Build From Source:  git clone https://github.com/mergebase/log4j-detector.git\ncd log4j-detector/\nmvn install\njava -jar target/log4j-detector-2021.12.17.jar\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:02.921846Z"}