CVE-2021-44228 PoC — Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints

Source

https://github.com/shamo0/CVE-2021-44228

Associated Vulnerability

Title:Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints (CVE-2021-44228)
Description:Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

Description

log4shell (CVE-2021-44228) scanning tool

Readme

# CVE-2021-44228 (log4shell) POC
---------------------
<h1 align="center">
  <img src="https://www.breezyscroll.com/wp-content/uploads/2021/12/log4j-exploit.jpeg" alt="Log4j-RCE-Scanner" width="80%"></a>
  <br>
</h1>

## log4j Scanning tool
This tool will help you identify remote code execution vulnerability (log4j) on your systems.


## Requirements
You will need to install [httpx](https://github.com/projectdiscovery/httpx), [subfinder](https://github.com/projectdiscovery/subfinder), [assetfinder](https://github.com/tomnomnom/assetfinder), [curl](https://github.com/curl/curl) and [amass](https://github.com/OWASP/Amass) in order to run the bash script.

## Installation
1. Simply git clone the repo or download the bash script <code>git clone https://github.com/shamo0/CVE-2021-44228.git</code>
2. change file permissions <code>chmod +x log4j_scanner.sh</code>
3. Run the bash script <code>./log4j_scanner.sh</code>

## Usage: 

<code>./log4j_scanner.sh -l subdomains.txt -i c6wvp482vtc10xx5bhnggdqp5neyyyyyb.interact.sh</code><br/>
<code>./log4j_scanner.sh -d vulnsite.com -i c6wvp482vtc10xx5bhnggdqp5neyyyyyb.interact.sh</code><br/>

<code>-h, --help              Help menu</code><br/>
<code>-l, --url-list          List of domain/subdomain/ip to be used for scanning.</code><br/>
<code>-d, --domain            The domain name to which all subdomains and itself will be checked with Subfinder & Assetfinder.</code><br/>
<code>-i, --inteactshdomain      interactsh domain address.</code><br/>



## References & Acknowledgements
* https://log4shell.huntress.com/
* https://github.com/adilsoybali/Log4j-RCE-Scanner
* https://nvd.nist.gov/vuln/detail/CVE-2021-44228

But also please note that
<h1 align="center">
  <img src="https://pbs.twimg.com/media/FGUwLYCX0AUUKNT.jpg" alt="Log4j-RCE-Scanner" width="80%"></a>
  <br>
</h1>

File Snapshot


 [4.0K]  /data/pocs/221054d0df2525aa1317d8698f0b1653f9e76210
├── [1.0K]  LICENSE
├── [7.8K]  log4j_scanner.sh
└── [1.8K]  README.md

0 directories, 3 files

Shenlong Bot has cached this for you

Remarks

1. It is advised to access via the original source first.

2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.

View subscription plans →

Goal Reached Thanks to every supporter — we hit 100%!