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
Dockerized honeypot for CVE-2021-44228.
Readme
# Log4Shell Honeypot
Dockerized honeypot for [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) based on Alpine, written in Python/Flask.
[](https://github.com/michaelsanford/Log4Shell-Honeypot/actions/workflows/snyk-container-analysis.yml)
[](https://github.com/michaelsanford/Log4Shell-Honeypot/actions/workflows/codeql-analysis.yml)
[](https://github.com/michaelsanford/Log4Shell-Honeypot/actions/workflows/pylint.yml)
## Detection Rule
The container responds with a plain login form.
Any request will be inspected for `${` (headers and body).
This triggers a critical-level log with the entire request (as a dict with tuples, which is JSON-ish).
## Event log
The event log will look like this (but as a single line):
```yaml
CRITICAL:<HONEYPOT_NAME>:{
'honeypot': '<HONEYPOT_NAME>',
'source': '172.17.0.1',
'headers': EnvironHeaders([
('Host', 'localhost:8080'),
('User-Agent', 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0'),
('Accept', 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8'),
('Accept-Language', 'en-CA,fr-CA;q=0.5'),
('Accept-Encoding', 'gzip, deflate'),
('Content-Type', 'application/x-www-form-urlencoded'),
('Content-Length', '45'),
('Origin', 'http://localhost:8080'),
('Connection', 'keep-alive'),
('Referer', 'http://localhost:8080/'),
('Upgrade-Insecure-Requests', '1'),
('Sec-Fetch-Dest', 'document'),
('Sec-Fetch-Mode', 'navigate'),
('Sec-Fetch-Site', 'same-origin'),
('Sec-Fetch-User', '?1')
]),
'body': [
('username', '${'),
('password', ''),
('submit', 'Submit Query')
]}
```
## Docker Quickstart
```shell
# x86_64
docker run -d -p 8080:8080 -e HONEYPOT_NAME="log4shell-honeypot" --name="log4shell-honeypot" msanford/log4shell-honeypot:latest
# ARM (e.g., Raspberry Pi)
docker run -d -p 8080:8080 -e HONEYPOT_NAME="log4shell-honeypot" --name="log4shell-honeypot" msanford/log4shell-honeypot:arm-latest
```
A `docker-compose.yml` fragment is also provided.
### Build
```shell
docker build -t log4shell-honeypot:latest .
```
# Acknowledgements
This is a modified fork of [BinaryDefense/log4shell-honeypot-flask](https://github.com/BinaryDefense/log4shell-honeypot-flask) 👏🏼.
File Snapshot
[4.0K] /data/pocs/407b5b585f1594667228ef0ffd631993e64d531c
├── [4.0K] app
│ └── [1.4K] app.py
├── [ 241] docker-compose.yml
├── [ 394] Dockerfile
├── [2.6K] README.md
├── [ 43] requirements.txt
└── [ 456] SECURITY.md
1 directory, 6 files
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 →