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.

Quick and dirty scanner, hitting common ports looking for Log4Shell (CVE-2021-44228) vulnerability

# log4shell_scanner
Quick and dirty scanner, hitting common ports looking for Log4Shell (CVE-2021-44228) vulnerability

This utilizes wget, curl, nmap, and the Log4Shell Huntress LDAP endpoint: https://log4shell.huntress.com/

If you need to scan a private subnet that doesn't have internet access, you can stand-up your own HTTP and LDAP server using the source code here: https://github.com/huntresslabs/log4shell-tester

 [4.0K]  /data/pocs/cffe2e21f2f10e5c3dd10ad36c9903ee964095ca
├── [2.2K]  log4shell_scanner.sh
└── [ 423]  README.md

0 directories, 2 files