CVE-2021-45046 PoC — Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack

Title:Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack (CVE-2021-45046)
Description:It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

Log4Shell(CVE-2021-45046) Sandbox Signature

# Log4Shell-Sandbox-Signature
Log4Shell(CVE-2021-45046) Sandbox Signature

Regex : https://github.com/back2root/log4shell-rex

- Cape Sandbox Signature

<p align="center">
   <img src="cape.png" title="Cape Sandbox Signature"/>
</p>

<p align="center">
   <img src="cape_traffic.png" title="Traffic"/>
</p>

- Cuckoo Sandbox Signature

<p align="center">
   <img src="cuckoo.png" title="Cuckoo Sandbox Signature"/>
</p>

 [4.0K]  /data/pocs/4c00685411ed4df03644b10e14c573f3d887ec01
├── [147K]  cape.png
├── [155K]  cape_traffic.png
├── [118K]  cuckoo.png
├── [1.3M]  cuckoo_traffic_LI (3).jpg
├── [ 34K]  LICENSE
├── [388K]  log4j.exe
├── [1.6K]  Log4shell_cape.py
├── [1.4K]  Log4Shell_cuckoo.py
└── [ 421]  README.md

0 directories, 9 files