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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

Source
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
CVE-2021-44228 
Readme
# Disclaimer
This project is for personal practice purposes only.
## CVE-2021-44228 log4j-shell-poc Exploit
This project demonstrates how to exploit the Apache Log4j vulnerability to gain access to a remote shell using a reverse shell command. 
## Getting Started
To get started with this project, follow the steps below:
## Prerequisites
* Virtual Box
* Docker
* JAVA SE Development kit 8u20
## Installing
1. clone this project from kozmer
git clone https://github.com/kozmer/log4j-shell-poc
2. Build the Docker image:
sudo docker build -t log4j-shell-poc 
3. Download and extract the Java SE Development kit 8u20 file:
sudo tar -xf jdk-8u20-linux-x64.tar.gz
## Exploiting the Vulnerability
1. Open a listener port on port 9001
2. Run the Python3 script that is downloaded from Github. The script will auto-setup the HTTP server and the LDAP server and create the payload that will be used to paste into the vulnerable parameter. The LDAP server contains the address link to our listener.
3. Run the Docker container with the vulnerable web app.
4. Open the web page that was set up previously and enter the malicious code into the user parameter.

At this stage, you will be able to connect to the web page shell. From here, you can browse and delete files. The creator has included a file called safeToDelete.tmp for you to test with. If this file contained sensitive information, a hacker could retrieve the data for malicious purposes or delete the file just for fun.
## Authors
* Kozmer https://github.com/kozmer 


File Snapshot

[4.0K] /data/pocs/d290c11b340deae324b4f6186a076309e7b5a1d4 ├── [ 14K] mitigation tehniques.docx ├── [1.5K] README.md ├── [1.7M] Step for exploiting.docx └── [ 72K] Vulnerabities description.docx 0 directories, 4 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.
    3. Mirroring, verifying, and maintaining this POC archive takes ongoing effort, so local snapshots are a paid feature. Your subscription keeps the archive online — thank you for the support. View subscription plans →