https://github.com/mablanco/docker-osmedeus
Docker image for Osmedeus, a fully automated offensive security tool for reconnaissance and vulnerability scanning
https://github.com/mablanco/docker-osmedeus
docker pentesting security
Last synced: 10 months ago
JSON representation
Docker image for Osmedeus, a fully automated offensive security tool for reconnaissance and vulnerability scanning
- Host: GitHub
- URL: https://github.com/mablanco/docker-osmedeus
- Owner: mablanco
- License: gpl-3.0
- Created: 2019-05-02T10:20:23.000Z (almost 7 years ago)
- Default Branch: main
- Last Pushed: 2024-10-27T11:34:22.000Z (over 1 year ago)
- Last Synced: 2024-10-27T21:06:02.734Z (over 1 year ago)
- Topics: docker, pentesting, security
- Language: Dockerfile
- Homepage:
- Size: 78.1 KB
- Stars: 100
- Watchers: 9
- Forks: 22
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# docker-osmedeus v4
## Description
Docker image for Osmedeus, a fully automated offensive security tool for reconnaissance and vulnerability scanning (). This image is built upon Debian's Bullseye slim image.
On 1st January 2022, Osmedeus' main developer (j3ssie) launched a beta of the new 4.0 version, which supersedes the previous v2 based on Django. While this README covers v4, the [READMEv2](READMEv2.md) file covers both the 1.5 and the 2.x versions.
From v4.0.0 on, the Docker image `latest` tag references the newest 4.x available version.
## How to use this image
The image launches Osmedeus' CLI tool without any arguments, so you have to provide your own to modify Osmedeus execution. Have a look at the inline help and the official documentation for basic and advanced usage examples.
This will show Osmedeus inline help:
```bash
~ docker run -it --rm mablanco/osmedeus
```
This will start an analysis on domain `example.com` with logs on the console and deleting the container after finishing:
```bash
~ docker run -it --rm mablanco/osmedeus osmedeus scan -t example.com
```
In case you want to persist the results of your analysis, you can create a volume for that purpose:
```bash
~ docker volume create osmedeus_workspaces
```
```bash
~ docker run -it --rm -v osmedeus_workspaces:/root/.osmedeus/workspaces mablanco/osmedeus osmedeus scan -t example.com
```
## Web UI
You can start the Web UI, as a daemonized process, with the following command:
```bash
~ docker run -d --name osmedeus-server -p 8000:8000 mablanco/osmedeus osmedeus server
```
Now the Web UI is accesible at `https://127.0.0.1:8000/`. You can access an already existing volume containing Osmedeus workspaces adding the above volume parameters.
The password to access the Web UI can be obtained executing this command:
```bash
~ docker exec -it osmedeus-server grep password /root/.osmedeus/config.yaml | head -1
```
## Building the image
Use the following command to build the image with the `latest` tag:
```bash
~ docker build -t mablanco/osmedeus .
```
In case you want to tag the image with a different version, use this command:
```bash
~ docker build -t mablanco/osmedeus: .
```