{"uuid": "b142199c-b371-4a03-9b0c-167813b3607b", "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/35345", "content": "Black Hat Ethical Hacking\nOffensive Security Tool: log4j-scan\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png Offensive Security Tool: log4j-scanPost Views: 490 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 4 Minutes\n\nOffensive Security Tool: log4j-scan GitHub Link log4j-scanA fully automated, accurate, and extensive scanner for finding vulnerable log4j hosts.\n\nhttps://www.blackhatethicalhacking.com/wp-content/uploads/2021/12/log4j.png DescriptionThis tool written by fullhunt, who have been researching the Log4J RCE (CVE-2021-44228) since it was released, and worked in preventing this vulnerability with their customers. They are open-sourcing an open detection and scanning tool for discovering and fuzzing for Log4J RCE CVE-2021-44228 vulnerability. This shall be used by security teams to scan their infrastructure for Log4J RCE, and also test for WAF bypasses that can result in achieving code execution on the organization\u2019s environment.\n\nIt supports DNS OOB callbacks out of the box, there is no need to setup a DNS callback server.\nSee Also: Log4j attackers switch to injecting Monero miners via RMI Features* Support for lists of URLs.\n* Fuzzing for more than 60 HTTP request headers (not only 3-4 headers as previously seen tools).\n* Fuzzing for HTTP POST Data parameters.\n* Fuzzing for JSON data parameters.\n* Supports DNS callback for vulnerability discovery and validation.\n* WAF Bypass payloads. Usage$ python3 log4j-scan.py -h\n[\u2022] CVE-2021-44228 - Apache Log4j RCE Scanner\n[\u2022] Scanner provided by FullHunt.io - The Next-Gen Attack Surface Management Platform.\n[\u2022] Secure your External Attack Surface with FullHunt.io. usage: log4j-scan.py [-h] [-u URL] [-l USEDLIST] [--request-type REQUEST_TYPE] [--headers-file HEADERS_FILE] [--run-all-tests] [--exclude-user-agent-fuzzing]\n                     [--wait-time WAIT_TIME] [--waf-bypass] [--dns-callback-provider DNS_CALLBACK_PROVIDER] [--custom-dns-callback-host CUSTOM_DNS_CALLBACK_HOST] optional arguments: -h, --help show this help message and exit -u URL, --url URL Check a single URL. -p PROXY, --proxy PROXY Send requests through proxy. -l USEDLIST, --list USEDLIST Check a list of URLs. --request-type REQUEST_TYPE Request Type: (get, post) - [Default: get]. --headers-file HEADERS_FILE Headers fuzzing list - [default: headers.txt]. --run-all-tests Run all available tests on each URL. --exclude-user-agent-fuzzing Exclude User-Agent header from fuzzing - useful to bypass weak checks on User-Agents. --wait-time WAIT_TIME Wait time after all URLs are processed (in seconds) - [Default: 5]. --waf-bypass Extend scans with WAF bypass payloads. --dns-callback-provider DNS_CALLBACK_PROVIDER DNS Callback provider (Options: dnslog.cn, interact.sh) - [Default: interact.sh]. --custom-dns-callback-host CUSTOM_DNS_CALLBACK_HOST Custom DNS Callback Host. \nSee Also: Complete Offensive Security and Ethical Hacking Course Scan a Single URL$ python3 log4j-scan.py -u https://log4j.lab.secbot.local Scan a Single URL using all Request Methods: GET, POST (url-encoded form), POST (JSON body)$ python3 log4j-scan.py -u https://log4j.lab.secbot.local \u2013run-all-tests Discover WAF bypasses on the environment.$ python3 log4j-scan.py -u https://log4j.lab.secbot.local \u2013waf-bypass Scan a list of URLs$ python3 log4j-scan.py -l urls.txt Installation$ pip3 install -r requirements.txt Docker Supportgit clone https://github.com/fullhunt/log4j-scan.git cd log4j-scan\nsudo docker build -t log4j-scan .\nsudo docker run -it --rm log4j-scan # With URL list \"urls.txt\" in current directory\ndocker run -it --rm -v $PWD:/data log4j-scan -l /data/urls.txt Legal DisclaimerT[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:02:03.760084Z"}