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

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.

Very simple Ansible playbook that scan filesystem for JAR files vulnerable to Log4Shell

# Log4j-CVE-2021-44228 scanner playbook

Very simple Ansible playbook that scan the filesystem for JAR files vulnerable to Log4Shell (CVE-2021-44228).

The result is saved in a CSV file in the local system.

## How to run

A value for the name of the CSV file must be passed via the `local_file` variable.

```bash
ansible-playbook --extra-vars "local_file=./jdni_dev.csv" log4j-cve-2021-44228.yml
```

 [4.0K]  /data/pocs/4f6e7f9b2bf48c26270dc0c3dd6318de7c4506ec
├── [1.9K]  log4j-cve-2021-44228.yml
└── [ 402]  README.md

0 directories, 2 files