pavanw3b / Sh00t

A Testing Environment for Manual Security Testers

Sh00t

• is a task manager to let you focus on performing security testing
• provides To Do checklists of test cases
• helps to create bug reports with customizable bug templates

Features:

• Dynamic Task Manager to replace simple editors or task management tools that are NOT meant for Security
• Automated, customizable Security test-cases Checklist to replace Evernote, OneNote or other tools which are NOT meant for Security
• Manage custom bug templates for different purposes and automatically generate bug report
• Support multiple Assessments & Projects to logically separate your different needs
• Use like a paper - Everything's saved automatically
• Export auto generated bug report into Markdown & submit blindly on HackerOne! (WIP)
• Integration with JIRA, ServiceNow - Coming soon
• Export bug report into Markdown - Coming soon
• Customize everything under-the-hood

Installation:

1. Install Docker if not available. Windows 10 Home users or older release users, refer the Alternative Installation instructions below.
2. Pull Sh00t Docker image: docker pull pavanw3b/sh00t:latest
3. Create Volume for data persistence across docker containers: docker volume create --name sh00t
4. Run the container: docker run -d -p 8000:8000 --name sh00t -v sh00t:/root/sh00t/db pavanw3b/sh00t:latest
5. Logon to http://127.0.0.1:8000/ on your favorite browser.
6. Login with sh00t / sh00t credentials
7. To stop: docker stop sht00t

Alternate Installations:

• Not comfortable with Docker yet? We got you covered. Installation without Docker
• Are you a Django-pro and want to set up everything on own? We got you covered too: Manual Setup
• Using a machine which does not have Hyper-V, like Windows Home? You can use Docker Toolbox and Docker Quickstart Terminal. Your Sh00t will run on the default IP of your docker: http://YOUR_DOCKER_IP:8000/. The IP Address will be displayed on the start of the Quickstart Terminal. You can also find it with docker-machine ls and docker-machine ip MACHINE_NAME.
• If you want to move to Docker version of Sh00t from a previous setup without loosing any of your existing data, you have to manually replace the /root/sh00/db/db.sqlite3 file on the docker container by your old sh00t setup.

Using Sh00t later:

1. Start the container: docker start sh00t
2. Logon to http://YOUR_IP:8000/ on your favorite browser
3. Login with sh00t / sh00t if you haven't changed it
4. Stop container if you care: docker stop sh00t

and repeat!

Note: Always use docker start and docker stop. You may loose your data if you remove the container or the volume.

Upgrade

It's important to keep your Sh00t to latest to avail the new features ang bug fixes.

1. Remove the existing container: docker container rm -f sh00t Do not worry, your data is safe unless you remove the docker volume.
2. Pull latest docker image: docker pull pavanw3b/sh00t:latest
3. Start a new container with the latest code, but still the old data: docker run -d -p 8000:8000 --name sh00t -v sh00t:/root/sh00t/db pavanw3b/sh00t:latest

Uninstallation

In the event you want to delete all Sh00t images, containers, and volumes, the following statements may be executed. Note: This is a destructive operation and cannot be undone.

1. Remove image: docker rmi pavanw3b/sh00t:latest
2. Remove container: docker rm sh00t
3. Remove volume: docker volume rm sh00t:/root/sh00t/db

Troubleshoot:

Sh00t is written in Python and powered by Django Web Framework. If you are stuck with any errors, Googling on the error message, should help you most of the times. If you are not sure, please file a new issue on github.

Glossary:

• Flag: A Flag is a target that is sh00ted at. It's a test case that needs to be tested. Flags are generated automatically based on the testing methodology chosen. The bug might or might not be found - but the goal is to aim and sh00t at it. Flag contains detailed steps for testing. If the bug is confirmed, then it's called a sh0t.
• Sh0t: Sh0ts are bugs. Typically Sh0t contain technical description of the bug, Affected Files/URLs, Steps To Reproduce and Fix Recommendation. Most of the contents of Sh0t is one-click generated and only the dynamic content like Affected Parameters, Steps has to be changed. Sh0ts can belong to Assessment.
• Assessment: Assessment is a testing assessment. It can be an assessment of an application, a program - up to the user the way wanted to manage. It's a part of project.
• Project: Project contains assessments. Project can be a logical separation of what you do. It can be different job, bug bounty, up to you to decide.
• Template: Templates are your bug templates. They are used with Sh0t. This is to replace the copy-paste work while you file a new Bug. Create Templates for all your bugs, leave the variables that will change in your actual bug report such as URL, Affected Area etc, which will be replaced when the Template is loaded in your Sh0t.
• Case Master: Cast Master is set of Test Cases. These are individual tests that you will perform on your target. Configuring Test Cases will help you manage your testing and Cover all the things you will need to in your Assessment. Every hacker will have his/her own Test Cases. Keep them short and easy to follow. Keeping a complete list of Test Cases in your Sh00t is the most important part of Using Sh00t. The Test Cases will become Flags that are to be Tested, when you are starting a new Assessment.
• Module Master: Modules are logical part of the tests. For example, User & session management is an example of Module. Modules are similar to category of the testing.
• Methodology Master: Methodology is your approach to your testing. OWASP Testing Guide V4 and Web Application Hacker Handbook (WAHH) are example Methodology and are shipped by default with Sh00t. You can create your own Methodology, Modules and Test Cases. You may have different Methodologies for your official work and personal bug bounty. Methodology will help you to separate them.

How does it work?

Begin with creating a new Assessment. Choose what methodology you want to test with. Today there are 330 test cases, grouped into 86 Flags, belonging to 13 Modules which are created with reference to "Web Application Hacker's Handbook" Testing Methodology. Modules & Flags can be handpicked & customized. Once Assessments are created with the Flags, now the tester has to test them either manually, or semi automated with the help of scanners, tools or however it's required, mark it "Done" on completion. While performing assessment we often come with custom test cases that is specific to certain scenario in the application. A new Flag can be created easily at any point of time.

Whenever a Flag is confirmed to be a valid bug, a Sh0t can be created. One can choose a bug template that matches best, and sh00t will auto fill the bug report based on the template chosen.

Who can use Sh00t?

• Application Security Engineers: Pentesting & Vulnerability Assessments
• Bug bounty hunters
• Independent Security Researchers
• Blue team, developers who fix
• Anybody who wants to hack

Screenshots:

Dashboard:

Working on a Flag:

Editing in fullscreen:

Choosing Methodology and Test Cases while creating a new Assessment:

Filing a bug pre-filled with a template:

Configruations:

Implementation details:

• Language: Python 3
• Framework: Django Web Framework
• Dependencies: Django REST Framework, djnago-tables2: Managed by /requirements.txt
• UI: Bootstrap - Responsive

Contribution:

• Pavan: @pavanw3b
• Aditya Ganapathy

Credits:

• Hari Valugonda
• Mohd Aqeel Ahmed
• Ajeeth Rakkappan