medicean/vulapps

★ 3,785ShellAudience · researcherComplexity · 2/5Setup · moderate

Mindmap

mindmap
  root((VulApps))
    What it does
      Vulnerable apps
      Docker-based
      CVE practice
    Software Covered
      Web servers
      CMS platforms
      Databases
    Use Cases
      Security research
      CTF training
      Detection testing
    Setup
      Docker pull
      Single command
      Instant teardown

mindmap root((VulApps)) What it does Vulnerable apps Docker-based CVE practice Software Covered Web servers CMS platforms Databases Use Cases Security research CTF training Detection testing Setup Docker pull Single command Instant teardown

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Spin up a vulnerable WordPress or Struts2 instance to practice exploiting a specific CVE in a safe local environment.

USE CASE 2

Build and test security detection tools against real broken software running in Docker containers.

USE CASE 3

Study a documented CVE by running the exact vulnerable software version and reproducing the exploit yourself.

USE CASE 4

Practice offensive security and capture-the-flag challenges using realistic broken software environments.

Tech stack

ShellDocker

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Docker installed locally, the README is in Chinese, though Docker commands are universal.

In plain English

VulApps is a collection of intentionally vulnerable application environments that security researchers and students can spin up on their own computers to practice finding and exploiting known software flaws. Each environment comes packaged as a Docker image, which means you can start a realistic broken version of a real product with a single command and tear it down just as quickly when you are done. The project covers a wide range of well-known software: web servers like Nginx and Tomcat, content management systems like WordPress and Joomla, frameworks like Spring and Struts2, databases like Redis and Memcached, and tools like Jenkins and JBoss. Most entries correspond to specific publicly documented security bugs, often referenced by their CVE identifier, so you can look up what the flaw is and then try to reproduce it in a safe, isolated setting. Using a specific environment follows a short two-step process. You look up the Docker image tag listed in the README for the vulnerability you want to study, pull the image from Docker Hub, and then run a container from it. Within seconds you have a live web application running locally with that vulnerability present and ready to test against. The project is written mainly in Shell and the Dockerfiles that define each image. It is aimed at people learning offensive security techniques, running capture-the-flag challenges, or building and testing detection tools. The README is in Chinese, though the technical commands are standard Docker syntax that any user familiar with containers can follow. A companion project called vulhub covers similar ground and is linked from the repository.

Copy-paste prompts

Prompt 1

Using VulApps, give me the Docker command to spin up a vulnerable Struts2 environment so I can practice exploiting CVE-2017-5638.

Prompt 2

How do I pull and run a VulApps Docker image for a vulnerable Redis instance to practice unauthorized access exploits?

Prompt 3

List the Spring Framework vulnerabilities available in VulApps and explain how to set up each one for local testing.

Prompt 4

I'm building a WAF detection tool. How do I use VulApps to set up a local target environment with a known SQL injection vulnerability?

Open on GitHub → Explain another repo

← medicean on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.