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/probablysecure/triage-cve-2021-44228-log4shell-log4j-
Vulnerability AnalysisLearning & EducationIncident ResponseLabs & Practice
GitHubprobablysecure/triage-cve-2021-44228-log4shell-log4j-

Triage-CVE-2021-44228-Log4Shell-Log4j-

Goal is to triage well known attack and learn how security teams quickly respond.

View Repository
264 months 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.

    989
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

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

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

    315

Explore all tools

Browse our collection of tools

View all tools →
Share

Triage: CVE-2021-44228 (Log4Shell / Log4j)

For this lab, the goal was to triage another well-known real-world vulnerability, Log4Shell, one of the most widely exploited vulnerabilities in recent years due to how common the affected library was across enterprise software.

Step 1: Open the CVE in NVD

I went to the National Vulnerability Database and looked up the CVE:

https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records

I searched for CVE-2021-44228 and opened the result page.

image

Step 2: Identify the asset and the exposure

After reading through the description, I answered a few basic questions to understand what's actually at risk:

  • What type of software is affected? Apache Log4j2, versions 2.0-beta9 through 2.15.0
  • Where would that software typically run? A server
  • What makes it risky in enterprises? Attackers can execute arbitrary code by using JNDI to reach an attacker-controlled LDAP server

Step 3: Record the CVSS base score and vector string

I found the CVSS score and vector string listed on the page:

image

Step 4: Break down the vector string

I went through the vector string piece by piece to see what each part actually meant:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
  • Attack Vector - Network
  • Attack Complexity - Low
  • Privileges Required - None
  • User Interaction - None
  • Scope - Changed
  • Confidentiality - High
  • Integrity - High
  • Availability - High

This is about as bad as a vector string gets: no privileges needed, no user interaction, reachable over the network, and it can even affect things outside the vulnerable component itself (Scope: Changed). That combination is part of why Log4Shell was treated as such an urgent, widespread issue when it was disclosed.

Step 5: Find the CWE category

I checked the Weakness Enumeration section on the NVD page for this CVE.

The CWE listed is CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement. In plain terms, this means the software takes input and evaluates it as part of an expression without properly checking it first, which is what let attackers slip in malicious JNDI lookups through normal log messages.

image image

Step 6: Answer a risk question

I considered whether I'd treat this as higher or lower risk under two different scenarios.

Scenario 1: The vulnerable software is live and reachable. Higher risk. This vulnerability lets an attacker access and modify EL (Expression Language) statements, directly affecting confidentiality and integrity.

Scenario 2: The vulnerable software is installed on a machine that's powered off and not reachable. Lower risk. If the vulnerable software can't be reached at all, confidentiality and integrity stay intact since there's no way for an attacker to interact with it.

Conclusion

Out of the CVEs I've triaged so far, this one stood out for how little an attacker needs to exploit it, no privileges, no user interaction, just network access, paired with the fact that the vulnerability could affect systems beyond the component itself. It's a good example of why Log4Shell caused such a widespread scramble across the industry when it came out.

Download Tool