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
Tools/GitHubGitHub/vorburger/log4j_cve-2021-44228
Vulnerability AnalysisExploitationWeb SecuritySupply Chain SecurityLearning & EducationCurated Resources
GitHubvorburger/log4j_cve-2021-44228

Log4j_CVE-2021-44228

Curated resource hub for Log4j CVE-2021-44228, covering detection, mitigation, exploitation, and dependency management strategies for the critical remote code execution vulnerability.

View Repository
31304 years agoNot yet reviewed

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.

    985
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    571
  • 3

    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.

    354
  • 4

    redforge

    cybersecurity91/redforge

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

    341
  • 5

    ARTEX

    baarai/artex

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

    324
  • 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.

    309

Explore all tools

Browse our collection of tools

View all tools →
Share

Log4j CVE-2021-44228

Solutions

Think about if you actually really require Log4j2 Core. Most likely, your own code (or some 3rd-party library you depend on) only need Log4j's Logging API façade - but can log to another back-end. You could therefore simply completely exclude the org.apache.logging.log4j:log4j-core dependency.

Use one of several available "Logging API Bridges" to connect (only) log4j-api with another Logging Implementation back-end:

  1. Log4j2-SLF4j-Logback using log4j-to-slf4j

  2. Log4j2-to-JUL from LOG4J2-3282 by me, as https://github.com/vorburger/Learning-Log4j2 illustrates.

This makes particular sense if you, or your Cloud Provider, has existing infrastructure for the respective back-end:

  • Google Cloud Logging Logback Appender, see on GitHub, also with Spring Framework integration

Background

  • https://logging.apache.org/log4j/2.x/security.html
  • https://github.com/advisories/GHSA-jfh8-c2jp-5v3q
  • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228

Detection & Scanning, Attack Surface

  • https://github.com/github/codeql/pull/7354
  • https://github.com/google/tsunami-security-scanner-plugins/issues/219
  • https://github.com/YfryTchsGD/Log4jAttackSurface (with Memes)

Mitigations

  • https://github.com/apache/logging-log4j2/pull/608
  • https://spring.io/blog/2021/12/10/log4j2-vulnerability-and-spring-boot
  • https://community.openhab.org/t/openhab-and-the-log4j-security-vulnerability/129901
  • https://github.com/vorburger/MariaDB4j/issues/509

Exploit

  • https://www.lunasec.io/docs/blog/log4j-zero-day/#exploit-steps
Download Tool