📢 This box is forked from righettod/toolbox-pentest-web and is modified to use it for intrusion purposes such as K8S pentesting.

Many thanks to https://github.com/righettod for this amazing work !!

🏭 Welcome to my forge

Note

📢 Even though this box is primarily intended for offensive operation, many tools and scripts can also be used for defensive purposes, for example, in CI/CD pipelines as security validation.

📑 This index can used to see all the scripts available.

👏 Image full credits go to Dirk Hoenes: https://pixabay.com/users/ptdh-275507.

🎯 The goal of this image is to provide an, always up to date "box", containing materials (tools + scripts) useful in the context of the assessment of a web-based application: site, API, etc. And now intrusion assessment !

⚙️ The image is based on the kali-rolling base image without any metapackage installed.

📱 Recently, I started to add content for mobile assessment to gather information/tools in a single box.

🔋 Health status

⚒️ Box enhancement approach

Projects

• SecLists.
• Nuclei templates.

Approach

sequenceDiagram
    participant T as Toolbox
    participant S as SecLists
    participant N as Nuclei templates
    alt Is a missing discovery dictionary entry
        T->>S: Propose a PR with the missing element
        S->>T: Get update from the GitHub repository once the PR is merged
    end
    alt Is a missing detection generic point
        T->>N: Propose a PR with the missing template
        N->>T: Get update from the GitHub repository once the PR is merged
    end
    alt Is a missing useful existing tool
        T->>T: Add the tool in a way to always use the latest version
    end       
    alt Is a missing specific need or without existing tool
        T->>T: Add a new custom script
    end       

Loading

🖥️ IDE VSCode

• Online in Gitpod
• Local in DevContainer

📚 What does it contain?

Build

The folder build contains utility internal scripts used to build the docker image.

Tools

All tools are installed in the folder /tools and a transfer zone between the container and the host has been defined via the folder /tools/reports.

Helper scripts

Note:

The index of all the scripts available is automatically updated, at each push on the master branch, via this workflow.

The folder scripts contains helper scripts for some operations using embedded tools.

Sandboxes with specific OS and/or runtime

The folder sandboxes contains utility docker files with specific OS/Runtime to create a specific sandbox.

The objective is to leverage the containerization to have a collection of quick sandboxes environment to test some specific behavior on a specific OS/runtime, for example, during a code review on an old version of a runtime (like PHP5).

The header of the dockerfile describes the target OS/runtime.

📡 All boxes are build and published to DockerHub every month (images starting with protyro/sandbox- name).

Command to use to build and/or run a sandbox:

💻 By default, a ZSH shell with Oh My Zsh is launched.

docker rmi -f protyro/[BoxName]
docker build --force-rm -t protyro/[BoxName] -f [Dockerfile] .
docker run --rm -v "[LOCAL_FOLDER_PATH]:/share" -i -t protyro/[BoxName]

Misc

The folder misc contains materials that can be used for testing specific cases like for example when an app is using:

• HTTP Signature.
• eIDAS certificate and key materials.
• RSA weak key pair:
  • RSA 512 bits private key / RSA 512 bits public key.
  • RSA 1024 bits private key / RSA 1024 bits public key.
• RSA JWK format key pair:
  • RSA 2048 bits private key / RSA 2048 bits public key / Corresponding JSON Web Key Sets JWKS file.

Templates

The folder templates contains several scripts/files that can be used as a basis for custom scripts to speed-up the implementation of a POC.

Dictionaries

The folder dictionaries contains several home-made custom dictionaries that can be used for discovery operations.

Technical hints

This file contains several technical hints for different kinds of context/issues/goals.

👀 It's a kind of cheat sheet.

🔨 Build image locally

Use the following set of commands:

$ git clone https://github.com/protyro/toolbox-pentest.git
$ cd toolbox-pentest
$ docker build . -t protyro/toolbox-pentest --file Dockerfile
...

📑 Container usage

On a docker host for direct access

Native docker on Linux or MacOS

# Create a volume to share files with the container (ex: reports)
$ docker volume create --name shared_space
$ docker volume inspect shared_space
# Run container
$ docker run -v shared_space:/tools/reports -p 127.0.0.1:80:80 -i -t protyro/toolbox-pentest /bin/zsh
$ docker run -v shared_space:/tools/reports -p 192.168.206.128:80:80 -p 192.168.206.128:443:443 -i -t protyro/toolbox-pentest /bin/zsh
# Build image into local cache
$ docker build -t protyro/toolbox-pentest .
# Remove image from local cache
$ docker rmi -f protyro/toolbox-pentest

Docker for Windows

rem Run container and defines a shared folder
C:\> docker run -v F:/SharedFolder:/tools/reports -p 127.0.0.1:80:80 -i -t protyro/toolbox-pentest /bin/zsh

For remote ssh access

Warning:

Private key to use for SSH authentication is here. This box is intended to be used as a toolbox for a short running period.

1. Run the container on the target docker host using the following command line:

$ docker run -p 22:22 protyro/toolbox-pentest
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
...

2. Access the container, via SSH, using the following command:

$ ssh -i ~/.ssh/ssh-private-key.pem root@[DOCKER_HOST_IP]
➜  ~

Add "StrictHostKeyChecking=no" in case of trouble with the remote keys because they are unique for each built image:

$ ssh -o "StrictHostKeyChecking=no" -i ~/.ssh/toolbox-ssh-private-key.pem root@[DOCKER_HOST_IP]
➜  ~

🚀 DockerHub

Image is published here each day or at each push on the master branch.