OWASP/wrongsecrets

Última atividade de origem registrada: 8 de setembro de 2026 às 08:08

Catálogo do SkillsMP atualizado: 5 de novembro de 2026 às 19:57

skills coletadas: 1

Estrelas no GitHub: 1.475
Forks no GitHub: 657

Instalar com um assistente de IA

Copie este prompt para o assistente de IA que você usa.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/OWASP/wrongsecrets.

README do repositório

Arquivo de origem do README: README.md

Ler o README original

Expandir README completo

# OWASP WrongSecrets [![Tweet](https://img.shields.io/badge/-Twitter-%232B90D9?style=for-the-badge&logo=x&logoColor=white)](https://twitter.com/intent/tweet?text=Want%20to%20dive%20into%20secrets%20management%20and%20do%20some%20hunting?%20try%20this&url=https://github.com/OWASP/wrongsecrets&hashtags=secretsmanagement,secrets,hunting,p0wnableapp,OWASP,WrongSecrets) [<img src="https://img.shields.io/badge/-MASTODON-%232B90D9?style=for-the-badge&logo=mastodon&logoColor=white">](https://tootpick.org/#text=Want%20to%20dive%20into%20secrets%20management%20and%20do%20some%20hunting?%20try%20this%0A%0Ahttps://github.com/OWASP/wrongsecrets%20%23secretsmanagement,%20%23secrets,%20%23hunting,%20%23p0wnableapp,%20%23OWASP,%20%23WrongSecrets) [<img src="https://img.shields.io/badge/-BLUESKY-%230085FF?style=for-the-badge&logo=bluesky&logoColor=white">](https://bsky.app/intent/compose?text=Want%20to%20dive%20into%20secrets%20management%20and%20do%20some%20hunting?%20try%20this%0A%0Ahttps://github.com/OWASP/wrongsecrets%20%23secretsmanagement%20%23secrets%20%23hunting%20%23p0wnableapp%20%23OWASP%20%23WrongSecrets) [<img src="https://img.shields.io/badge/-LINKEDIN-0077B5?style=for-the-badge&logo=linkedin&logoColor=white">](https://www.linkedin.com/shareArticle/?url=https://www.github.com/OWASP/wrongsecrets&title=OWASP%20WrongSecrets) [![Java checkstyle and testing](https://github.com/OWASP/wrongsecrets/actions/workflows/main.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/main.yml) [![Pre-commit](https://github.com/OWASP/wrongsecrets/actions/workflows/pre-commit.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/pre-commit.yml) [![Terraform FMT](https://github.com/OWASP/wrongsecrets/actions/workflows/terraform.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/terraform.yml) [![CodeQL](https://github.com/OWASP/wrongsecrets/actions/workflows/codeql-analysis.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/codeql-analysis.yml) [![Dead Link Checker](https://github.com/OWASP/wrongsecrets/actions/workflows/link_checker.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/link_checker.yml) [![Javadoc and Swaggerdoc generator](https://github.com/OWASP/wrongsecrets/actions/workflows/java_swagger_doc.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/java_swagger_doc.yml) [![Test Heroku with cypress](https://github.com/OWASP/wrongsecrets/actions/workflows/heroku_tests.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/heroku_tests.yml) [![Build Dev Container](https://github.com/OWASP/wrongsecrets/actions/workflows/build-devcontainer.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/build-devcontainer.yml) [![Test minikube script (k8s)](https://github.com/OWASP/wrongsecrets/actions/workflows/minikube-k8s-test.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/minikube-k8s-test.yml) [![Test minikube script (k8s&vault)](https://github.com/OWASP/wrongsecrets/actions/workflows/minikube-vault-test.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/minikube-vault-test.yml) [![Docker container test](https://github.com/OWASP/wrongsecrets/actions/workflows/container_test.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/container_test.yml) [![Test container on podman](https://github.com/OWASP/wrongsecrets/actions/workflows/container-alts-test.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/container-alts-test.yml) [![DAST with ZAP](https://github.com/OWASP/wrongsecrets/actions/workflows/dast-zap-test.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/dast-zap-test.yml) [![PR Preview and Visual Diff](https://github.com/OWASP/wrongsecrets/actions/workflows/pr-preview.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/pr-preview.yml) [![Build Preview](https://github.com/OWASP/wrongsecrets/actions/workflows/build-preview.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/build-preview.yml) [![Visual Diff](https://github.com/OWASP/wrongsecrets/actions/workflows/visual-diff.yml/badge.svg)](https://github.com/OWASP/wrongsecrets/actions/workflows/visual-diff.yml) [![OWASP Production Project](https://img.shields.io/badge/OWASP-production%20project-48A646.svg)](https://owasp.org/projects/) [![OpenSSF Best Practices](https://bestpractices.coreinfrastructure.org/projects/7024/badge)](https://bestpractices.coreinfrastructure.org/projects/7024) [![Discussions](https://img.shields.io/github/discussions/OWASP/wrongsecrets)](https://github.com/OWASP/wrongsecrets/discussions) [![Docker pulls](https://img.shields.io/docker/pulls/jeroenwillemsen/wrongsecrets.svg)](https://hub.docker.com/r/jeroenwillemsen/wrongsecrets) Welcome to the OWASP WrongSecrets game! The game is packed with real life examples of how to _not_ store secrets in your software. Each of these examples is captured in a challenge, which you need to solve using various tools and techniques. Solving these challenges will help you recognize common mistakes & can help you to reflect on your own secrets management strategy. Can you solve all the challenges? Try some of them on [our Heroku demo environment](https://wrongsecrets.herokuapp.com/). Want to play the other challenges? Read the instructions on how to set them up below. ## 🚀 Quick Start **New to WrongSecrets? Start here:** 1. **Try Online First**: Visit our [Heroku demo](https://wrongsecrets.herokuapp.com/) to get familiar with the challenges 2. **Run Locally**: Use Docker for the full experience with all challenges: ```bash docker run -p 8080:8080 -p 8090:8090 jeroenwillemsen/wrongsecrets:latest-no-vault ``` Then open [http://localhost:8080](http://localhost:8080) 3. **Want to see what's ahead?** Try our bleeding-edge master container with the latest features: ```bash docker run -p 8080:8080 -p 8090:8090 ghcr.io/owasp/wrongsecrets/wrongsecrets-master:latest-master ``` ⚠️ *Note: This is a development version and may be unstable* 4. **Advanced Setup**: For cloud challenges and Kubernetes exercises, see the detailed instructions below **What you'll learn:** - Common secrets management mistakes - How to identify exposed credentials - Best practices for securing secrets - Tools and techniques for secret detection **How it works:** This repository contains **intentionally vulnerable code and configuration files** with real and fake secrets hidden throughout the codebase. You'll examine source code, configuration files, Docker containers, and cloud deployments to discover these secrets. Each challenge teaches you different ways secrets can be accidentally exposed in real-world applications. ![screenshotOfChallenge1](/images/screenshot.png) ## 📋 Prerequisites **For basic usage:** - A web browser - Docker (for local setup) - [Install here](https://docs.docker.com/get-docker/) **For advanced setups:** - Kubernetes/Minikube - [Install here](https://minikube.sigs.k8s.io/docs/start/) - Cloud account (AWS/GCP/Azure) for cloud challenges - Command line familiarity <a href="https://github.com/vshymanskyy/StandWithUkraine/blob/main/README.md"><img src="https://raw.githubusercontent.com/vshymanskyy/StandWithUkraine/main/banner2-no-action.svg" /></a> ## Table of contents ### 🎯 Getting Started - [Quick Start](#-quick-start) - [Prerequisites](#-prerequisites) - [Support](#support) ### 🐳 Deployment Options - [Basic docker exercises](#basic-docker-exercises) - [Running these on Heroku](#running-these-on-heroku) - [Running these on Render.io](#running-these-on-renderio) - [Running these on Railway](#running-these-on-railway) - [Basic K8s exercise](#basic-k8s-exercise) - [Minikube based](#minikube-based) - [k8s based](#k8s-based) - [Vault exercises with minikube](#vault-exercises-with-minikube) ### ☁️ Cloud Challenges - [Cloud Challenges](#cloud-challenges) - [Running WrongSecrets in AWS](#running-wrongsecrets-in-aws) - [Running WrongSecrets in GCP](#running-wrongsecrets-in-gcp) - [Running WrongSecrets in Azure](#running-wrongsecrets-in-azure) - [Running Challenge15 in your own cloud only](#running-challenge15-in-your-own-cloud-only) ### 🎮 Advanced Usage - [Do you want to play without guidance?](#do-you-want-to-play-without-guidance-or-spoils) - [CTF](#ctf) - [CTFD Support](#ctfd-support) - [FBCTF Support](#fbctf-support-experimental) - [Use OWASP WrongSecrets as a secret detection benchmark](#use-owasp-wrongsecrets-as-a-secret-detection-benchmark) ### 👨‍💻 Development & Contribution - [Notes on development](#notes-on-development) - [Spring Boot 4 adoption checklist](docs/SPRING_BOOT_4_ADOPTION_CHECKLIST.md) - [Dependency management](#dependency-management) - [Get the project started in IntelliJ IDEA](#get-the-project-started-in-intellij-idea) - [Automatic reload during development](#automatic-reload-during-development) - [How to add a Challenge](#how-to-add-a-challenge) - [Local testing](#local-testing) - [Local Automated testing](#Local-automated-testing) - [Want to disable challenges in your own release?](#want-to-disable-challenges-in-your-own-release) ### 📚 Resources & Community - [Special thanks & Contributors](#special-thanks--contributors) - [Sponsorships](#sponsorships) - [Help Wanted](#help-wanted) - [Further reading on secrets management](#further-reading-on-secrets-management) ## Support Need support? Contact us via [OWASP Slack](https://owasp.slack.com/archives/C02KQ7D9XHR) for which you sign up [here](https://owasp.org/slack/invite) , file a [PR](https://github.com/OWASP/wrongsecrets/pulls), file an [issue](https://github.com/OWASP/wrongsecrets/issues) , or use [discussions](https://github.com/OWASP/wrongsecrets/discussions). Please note that this is an OWASP volunteer based project, so it might take a little while before we respond. Copyright (c) 2020-2025 Jeroen Willemsen and WrongSecrets contributors. ## 🛤️ Choose Your Path Not sure which setup is right for you? Here's a quick guide: | **I want to...** | **Recommended Setup** | **Challenges Available** | |------------------|----------------------|--------------------------| | Try it quickly online | [Container running on Heroku](https://www.wrongsecrets.com/) | Basic challenges (0-4, 8, 12-32, 34-43, 49-52, 54-66, 68-73) | | Run locally with Docker | [Basic Docker](#basic-docker-exercises) | Same as above, but on your machine | | Learn Kubernetes secrets | [K8s/Minikube Setup](#basic-k8s-exercise) | Kubernetes challenges (0-6, 8, 12-43, 48-66, 68-72, 74) | | Practice with cloud secrets | [Cloud Challenges](#cloud-challenges) | All challenges (0-72) | | Run a workshop/CTF | [CTF Setup](#ctf) | Customizable challenge sets | | Contribute to the project | [Development Setup](#notes-on-development) | All challenges + development tools | ## Basic docker exercises _Can be used for challenges 0-4, 8, 12-32, 34-43, 49-52, 54-66, 68-73_ For the basic docker exercises you currently require: - Docker [Install from here](https://docs.docker.com/get-docker/) - Some Browser that can render HTML You can install it by doing: ```bash docker run -p 8080:8080 -p 8090:8090 jeroenwillemsen/wrongsecrets:latest-no-vault ``` **🚀 Want to try the bleeding-edge version?** If you want to see what's coming in the next release, you can use our automatically-built master container: ```bash docker run -p 8080:8080 -p 8090:8090 ghcr.io/owasp/wrongsecrets/wrongsecrets-master:latest-master ``` ⚠️ **Warning**: This is a development version built from the latest master branch and may contain experimental features or instabilities. **📝 Note on Ports:** - Port **8080**: Main application (challenges 0-73) - Port **8090**: MCP server (required for Challenge 60) **📝 Note on Challenge 62 (Google Drive MCP):** Challenge 62 requires a Google Service Account to be configured for full functionality. See [docs/CHALLENGE62_GOOGLE_DRIVE_SETUP.md](docs/CHALLENGE62_GOOGLE_DRIVE_SETUP.md) for setup instructions. Without configuration, the challenge will show a placeholder message. Now you can try to find the secrets by means of solving the challenge offered at the links below <details> <summary>all the links for docker challenges (click triangle to open the block). </summary> - [localhost:8080/challenge/challenge-0](http://localhost:8080/challenge/challenge-0) - [localhost:8080/challenge/challenge-1](http://localhost:8080/challenge/challenge-1) - [localhost:8080/challenge/challenge-2](http://localhost:8080/challenge/challenge-2) - [localhost:8080/challenge/challenge-3](http://localhost:8080/challenge/challenge-3) - [localhost:8080/challenge/challenge-4](http://localhost:8080/challenge/challenge-4) - [localhost:8080/challenge/challenge-8](http://localhost:8080/challenge/challenge-8) - [localhost:8080/challenge/challenge-12](http://localhost:8080/challenge/challenge-12) - [localhost:8080/challenge/challenge-13](http://localhost:8080/challenge/challenge-13) - [localhost:8080/challenge/challenge-14](http://localhost:8080/challenge/challenge-14) - [localhost:8080/challenge/challenge-15](http://localhost:8080/challenge/challenge-15) - [localhost:8080/challenge/challenge-16](http://localhost:8080/challenge/challenge-16) - [localhost:8080/challenge/challenge-17](http://localhost:8080/challenge/challenge-17) - [localhost:8080/challenge/challenge-18](http://localhost:8080/challenge/challenge-18) - [localhost:8080/challenge/challenge-19](http://localhost:8080/challenge/challenge-19) - [localhost:8080/challenge/challenge-20](http://localhost:8080/challenge/challenge-20) - [localhost:8080/challenge/challenge-21](http://localhost:8080/challenge/challenge-21) - [localhost:8080/challenge/challenge-22](http://localhost:8080/challenge/challenge-22) - [localhost:8080/challenge/challenge-23](http://localhost:8080/challenge/challenge-23) - [localhost:8080/challenge/challenge-24](http://localhost:8080/challenge/challenge-24) - [localhost:8080/challenge/challenge-25](http://localhost:8080/challenge/challenge-25) - [localhost:8080/challenge/challenge-26](http://localhost:8080/challenge/challenge-26) - [localhost:8080/challenge/challenge-27](http://localhost:8080/challenge/challenge-27) - [localhost:8080/challenge/challenge-28](http://localhost:8080/challenge/challenge-28) - [localhost:8080/challenge/challenge-29](http://localhost:8080/challenge/challenge-29) - [localhost:8080/challenge/challenge-30](http://localhost:8080/challenge/challenge-30) - [localhost:8080/challenge/challenge-31](http://localhost:8080/challenge/challenge-31) - [localhost:8080/challenge/challenge-32](http://localhost:8080/challenge/challenge-32) - [localhost:8080/challenge/challenge-34](http://localhost:8080/challenge/challenge-34) - [localhost:8080/challenge/challenge-35](http://localhost:8080/challenge/challenge-35) - [localhost:8080/challenge/challenge-36](http://localhost:8080/challenge/challenge-36) - [localhost:8080/challenge/challenge-37](http://localhost:8080/challenge/challenge-37) - [localhost:8080/challenge/challenge-38](http://localhost:8080/challenge/challenge-38) - [localhost:8080/challenge/challenge-39](http://localhost:8080/challenge/challenge-39) - [localhost:8080/challenge/challenge-40](http://localhost:8080/challenge/challenge-40) - [localhost:8080/challenge/challenge-41](http://localhost:8080/challenge/challenge-41) - [localhost:8080/challenge/challenge-42](http://localhost:8080/challenge/challenge-42) - [localhost:8080/challenge/challenge-43](http://localhost:8080/challenge/challenge-43) - [localhost:8080/challenge/challenge-49](http://localhost:8080/challenge/challenge-49) - [localhost:8080/challenge/challenge-50](http://localhost:8080/challenge/challenge-50) - [localhost:8080/challenge/challenge-51](http://localhost:8080/challenge/challenge-51) - [localhost:8080/challenge/challenge-52](http://localhost:8080/challenge/challenge-52) - [localhost:8080/challenge/challenge-54](http://localhost:8080/challenge/challenge-54) - [localhost:8080/challenge/challenge-55](http://localhost:8080/challenge/challenge-55) - [localhost:8080/challenge/challenge-56](http://localhost:8080/challenge/challenge-56) - [localhost:8080/challenge/challenge-57](http://localhost:8080/challenge/challenge-57) - [localhost:8080/challenge/challenge-58](http://localhost:8080/challenge/challenge-58) - [localhost:8080/challenge/challenge-59](http://localhost:8080/challenge/challenge-59) - [localhost:8080/challenge/challenge-60](http://localhost:8080/challenge/challenge-60) - [localhost:8080/challenge/challenge-61](http://localhost:8080/challenge/challenge-61) - [localhost:8080/challenge/challenge-62](http://localhost:8080/challenge/challenge-62) - [localhost:8080/challenge/challenge-63](http://localhost:8080/challenge/challenge-63) - [localhost:8080/challenge/challenge-64](http://localhost:8080/challenge/challenge-64) - [localhost:8080/challenge/challenge-65](http://localhost:8080/challenge/challenge-65) - [localhost:8080/challenge/challenge-66](http://localhost:8080/challenge/challenge-66) - [localhost:8080/challenge/challenge-68](http://localhost:8080/challenge/challenge-68) - [localhost:8080/challenge/challenge-69](http://localhost:8080/challenge/challenge-69) - [localhost:8080/challenge/challenge-70](http://localhost:8080/challenge/challenge-70) - [localhost:8080/challenge/challenge-71](http://localhost:8080/challenge/challenge-71) - [localhost:8080/challenge/challenge-72](http://localhost:8080/challenge/challenge-72) - [localhost:8080/challenge/challenge-73](http://localhost:8080/challenge/challenge-73) </details> Note that these challenges are still very basic, and so are their explanations. Feel free to file a PR to make them look better ;-). ### Running these on Heroku You can test them out at [https://wrongsecrets.herokuapp.com/](https://wrongsecrets.herokuapp.com/) as well! The folks at Heroku have given us an awesome open source support package, which allows us to run the app for free there, where it is almost always up. Still, please do not fuzz and/or try to bring it down: you would be spoiling it for others that want to testdrive it. Use [this link](https://wrongsecrets.herokuapp.com/) to use our hosted version of the app. If you want to host it on Heroku yourself (e.g., for running a training), you can do so by clicking [this link](https://heroku.com/deploy?template=https://github.com/OWASP/wrongsecrets/tree/master). Please be aware that this will incur costs for which this project and/or its maintainers cannot be held responsible. ### Running these on Render.io *status: experimental* You can test them out at [https://wrongsecrets.onrender.com/](https://wrongsecrets.onrender.com/). Please understand that we run on a free-tier instance, we cannot give any guarantees. Please do not fuzz and/or try to bring it down: you would be spoiling it for others that want to testdrive it. Want to deploy yourself with Render? Click the button below: [![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy?repo=https://github.com/OWASP/wrongsecrets) ### Running these on Railway *status: maintained by [alphasec.io](https://github.com/alphasecio)* If you want to host WrongSecrets on Railway, you can do so by deploying [this one-click template](https://railway.com/deploy/McqJ_j?referralCode=I07F1). Railway does not offer an always-free plan anymore, but the free trial is good enough to test-drive this before you decide to upgrade. If you need a step-by-step companion guide, see [this blog post](https://alphasec.io/test-your-secret-management-skills-with-owasp-wrongsecrets/). [![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/deploy/McqJ_j?referralCode=I07F1j) ## Basic K8s exercise _Can be used for challenges 0-6, 8, 12-43, 48-72, 74_ ### Minikube based Make sure you have the following installed: - Docker [Install from here](https://docs.docker.com/get-docker/) - Minikube [Install from here](https://minikube.sigs.k8s.io/docs/start/) The K8S setup currently is based on using Minikube for local fun. You can use the commands below from the root of the project: ```bash minikube start kubectl apply -f k8s/secrets-config.yml kubectl apply -f k8s/secrets-secret.yml kubectl apply -f k8s/challenge33.yml kubectl apply -f k8s/challenge53/secret-challenge53.yml echo "Setting up the bitnami sealed secret controler" kubectl apply -f https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.27.0/controller.yaml kubectl apply -f k8s/sealed-secret-controller.yaml kubectl apply -f k8s/main.key kubectl delete pod -n kube-system -l name=sealed-secrets-controller kubectl create -f k8s/sealed-challenge48.json echo "finishing up the sealed secret controler part" kubectl -n kube-system wait --for=condition=ready pod -l name=sealed-secrets-controller --timeout=60s kubectl wait --for=create secret/secret48 --timeout=60s kubectl apply -f k8s/secret-challenge-deployment.yml while [[ $(kubectl get pods -l app=secret-challenge -o 'jsonpath={..status.conditions[?(@.type=="Ready")].status}') != "True" ]]; do echo "waiting for secret-challenge" && sleep 2; done kubectl expose deployment secret-challenge --type=LoadBalancer --port=8080 minikube service secret-challenge ``` Alternatively you can do : ```bash ./k8s-vault-minikube-start.sh ``` now you can use the provided IP address and port to further play with the K8s variant (instead of localhost). - [localhost:8080/challenge/challenge-5](http://localhost:8080/challenge/challenge-5) - [localhost:8080/challenge/challenge-6](http://localhost:8080/challenge/challenge-6) - [localhost:8080/challenge/challenge-33](http://localhost:8080/challenge/challenge-33) - [localhost:8080/challenge/challenge-48](http://localhost:8080/challenge/challenge-48) - [localhost:8080/challenge/challenge-53](http://localhost:8080/challenge/challenge-53) ### k8s based Want to run vanilla on your own k8s? Use the commands below: ```bash kubectl apply -f k8s/secrets-config.yml kubectl apply -f k8s/secrets-secret.yml echo "Setting up the bitnami sealed secret controler" kubectl apply -f https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.27.0/controller.yaml kubectl apply -f k8s/sealed-secret-controller.yaml kubectl apply -f k8s/main.key kubectl delete pod -n kube-system -l name=sealed-secrets-controller kubectl create -f k8s/sealed-challenge48.json echo "finishing up the sealed secret controler part" kubectl -n kube-system wait --for=condition=ready pod -l name=sealed-secrets-controller --timeout=60s kubectl wait --for=create secret/secret48 --timeout=60s kubectl apply -f k8s/challenge33.yml kubectl apply -f k8s/secret-challenge-deployment.yml while [[ $(kubectl get pods -l app=secret-challenge -o 'jsonpath={..status.conditions[?(@.type=="Ready")].status}') != "True" ]]; do echo "waiting for secret-challenge" && sleep 2; done kubectl port-forward \ $(kubectl get pod -l app=secret-challenge -o jsonpath="{.items[0].metadata.name}") \ 8080:8080 ``` now you can use the provided IP address and port to further play with the K8s variant (instead of localhost). - [localhost:8080/challenge/challenge-5](http://localhost:8080/challenge/challenge-5) - [localhost:8080/challenge/challenge-6](http://localhost:8080/challenge/challenge-6) - [localhost:8080/challenge/challenge-33](http://localhost:8080/challenge/challenge-33) - [localhost:8080/challenge/challenge-48](http://localhost:8080/challenge/challenge-48) ## Vault exercises with minikube _Can be used for challenges 0-8, 12-46, 48-72_ Make sure you have the following installed: - minikube with docker (or comment out line 8 and work at your own k8s setup), - docker, - helm [Install from here](https://helm.sh/docs/intro/install/), - kubectl [Install from here](https://kubernetes.io/docs/tasks/tools/), - jq [Install from here](https://stedolan.github.io/jq/download/), - vault [Install from here](https://developer.hashicorp.com/vault/install), - grep, Cat, and Sed Run `./k8s-vault-minikube-start.sh`, when the script is done, then the challenges will wait for you at <http://localhost:8080> . This will allow you to run challenges 0-8, 12-66. When you stopped the `k8s-vault-minikube-start.sh` script and want to resume the port forward run: `k8s-vault-minikube-resume.sh`. This is because if you run the start script again it will replace the secret in the vault and not update the secret-challenge application with the new secret. ## Cloud Challenges _Can be used for challenges 0-72_ **READ THIS**: Given that the exercises below contain IAM privilege escalation exercises, never run this on an account which is related to your production environment or can influence your account-over-arching resources. ### Running WrongSecrets in AWS Follow the steps in [the README in the AWS subfolder](aws/README.md). ### Running WrongSecrets in GCP Follow the steps in [the README in the GCP subfolder](gcp/README.md). ### Running WrongSecrets in Azure Follow the steps in [the README in the Azure subfolder](azure/README.md). ### Running Challenge15 in your own cloud only When you want to include your own Canarytokens for your cloud-deployment, do the following: 1. Fork the project. 2. Make sure you use the [GCP ingress](/gcp/k8s-vault-gcp-ingress-start.sh) or [AWS ingress](aws/k8s-aws-alb-script.sh) scripts to generate an ingress for your project. 3. Go to [canarytokens.org](https://canarytokens.org/generate) and select `AWS Keys`, in the webHook URL field add `<your-domain-created-at-step1>/canaries/tokencallback`. 4. Encrypt the received credentials so that [Challenge15](/src/main/java/org/owasp/wrongsecrets/challenges/docker/Challenge15.java) can decrypt them again. 5. Commit the unencrypted and encrypted materials to Git and then commit again without the decrypted materials. 6. Adapt the hints of Challenge 15 in your fork to point to your fork. 7. Create a container and push it to your registry 8. Override the K8s definition files for either [AWS](/aws/k8s/secret-challenge-vault-deployment.yml) or [GCP](/gcp/k8s/secret-challenge-vault-deployment.yml.tpl). ## Do you want to play without guidance or spoils? Each challenge has a `Show hints` button and a `What's wrong?` button. These buttons help to simplify the challenges and give explanation to the reader. Though, the explanations can spoil the fun if you want to do this as a hacking exercise. Therefore, you can manipulate them by overriding the following settings in your env: - `hints_enabled=false` will turn off the `Show hints` button. - `reason_enabled=false` will turn of the `What's wrong?` explanation button. - `spoiling_enabled=false` will turn off the `/spoil/challenge-x` endpoint (where `x` is the short-name of the challenge). ## Enabling Swaggerdocs and UI You can enable Swagger documentation and the Swagger UI by overriding the `SPRINGDOC_UI` and `SPRINGDOC_DOC` when running the Docker container. ## Special thanks & Contributors Leaders: - [Ben de Haan @bendehaan](https://www.github.com/bendehaan) - [Jeroen Willemsen @commjoen](https://www.github.com/commjoen) Top contributors: - [Jannik Hollenbach @J12934](https://www.github.com/J12934) - [Puneeth Y @puneeth072003](https://www.github.com/puneeth072003) - [Joss Sparkes @RemakingEden](https://www.github.com/RemakingEden) Contributors: - [Nanne Baars @nbaars](https://www.github.com/nbaars) - [Marcin Nowak @drnow4u](https://www.github.com/drnow4u) - [Rodolfo Neves @roddas](https://www.github.com/roddas) - [O @osamamagdy](https://www.github.com/osamamagdy) - [Pastekitoo @Pastekitoo](https://www.github.com/Pastekitoo) - [za @za](https://www.github.com/za) - [Sandeep @youknowme19](https://www.github.com/youknowme19) - [Divyanshu Dev @Novice-expert](https://www.github.com/Novice-expert) - [Anirban Ghosh @kekubhai](https://www.github.com/kekubhai) - [Tibor Hercz @tiborhercz](https://www.github.com/tiborhercz) - [sandeshkuldharme1 @sandeshkuldharme1](https://www.github.com/sandeshkuldharme1) - [Shubham Patel @Shubham-Patel07](https://www.github.com/Shubham-Patel07) - [Adarsh A @adarsh-a-tw](https://www.github.com/adarsh-a-tw) - [Chris Elbring Jr. @neatzsche](https://www.github.com/neatzsche) - [Diamond Rivero @diamant3](https://www.github.com/diamant3) - [Norbert Wolniak @nwolniak](https://www.github.com/nwolniak) - [Jeffy123-zhu @Jeffy123-zhu](https://www.github.com/Jeffy123-zhu) - [Robert Felber @rfelber](https://www.github.com/rfelber) - [Filip Chyla @fchyla](https://www.github.com/fchyla) - [Seershan Mitra @seershan](https://www.github.com/seershan) - [Vineeth Jagadeesh @djvinnie](https://www.github.com/djvinnie) - [Dmitry Litosh @Dlitosh](https://www.github.com/Dlitosh) - [Mahaputra Ilham Awal @mahaputrailhamawal](https://www.github.com/mahaputrailhamawal) - [Turjo Chowdhury @turjoc120](https://www.github.com/turjoc120) - [SndR @SndR85](https://www.github.com/SndR85) - [alphasec @alphasecio](https://www.github.com/alphasecio) - [Bhushan Agrawal @bhushan4work](https://www.github.com/bhushan4work) - [CaduRoriz @CaduRoriz](https://www.github.com/CaduRoriz) - [Josh Grossman @tghosth](https://www.github.com/tghosth) - [Miracle Owolabi @ArksherX](https://www.github.com/ArksherX) - [Madhu Akula @madhuakula](https://www.github.com/madhuakula) - [Mike Woudenberg @mikewoudenberg](https://www.github.com/mikewoudenberg) - [Spyros @northdpole](https://www.github.com/northdpole) - [Satyam Pandey @SatyamPandey-07](https://www.github.com/SatyamPandey-07) - [Muhammad Moeed Ur Rehman Khan @moeedrehman135](https://www.github.com/moeedrehman135) - [RubenAtBinx @RubenAtBinx](https://www.github.com/RubenAtBinx) - [Alex Bender @alex-bender](https://www.github.com/alex-bender) - [Arpit Jain @arpitjain099](https://www.github.com/arpitjain099) - [Tuer·maimaitiaili Ba @bte808](https://www.github.com/bte808) - [Danny Lloyd @dannylloyd](https://www.github.com/dannylloyd) - [Fern @f3rn0s](https://www.github.com/f3rn0s) - [Rick M @kingthorin](https://www.github.com/kingthorin) - [Bobo @lb1192176991-lab](https://www.github.com/lb1192176991-lab) - [Nicolas Humblot @nhumblot](https://www.github.com/nhumblot) - [Shivam Saini @shivam-saini18](https://www.github.com/shivam-saini18) - [Simranjit8933 @Simranjit8933](https://www.github.com/Simranjit8933) - [Shlomo Zalman Heigh @szh](https://www.github.com/szh) - [Jeff Tong @Wind010](https://www.github.com/Wind010) Testers: - [Dave van Stein @davevs](https://www.github.com/davevs) - [Marcin Nowak @drnow4u](https://www.github.com/drnow4u) - [Marc Chang Sing Pang @mchangsp](https://www.github.com/mchangsp) - [Vineeth Jagadeesh @djvinnie](https://www.github.com/djvinnie) Translators: - [LittlePrimate @LittlePrimate](https://www.github.com/LittlePrimate) - [S3DFX-CYBER @S3DFX-CYBER](https://www.github.com/S3DFX-CYBER) - [Bhushan Agrawal @bhushan4work](https://www.github.com/bhushan4work) Special thanks: - [Madhu Akula @madhuakula @madhuakula](https://www.github.com/madhuakula) - [Nanne Baars @nbaars @nbaars](https://www.github.com/nbaars) - [Bjorn Kimminich @bkimminich](https://www.github.com/bkimminich) - [Dan Gora @devsecops](https://www.github.com/devsecops) - [Xiaolu Dai @saragluna](https://www.github.com/saragluna) - [Jonathan Giles @jonathanGiles](https://www.github.com/jonathanGiles) ### Sponsorships We would like to thank the following parties for helping us out: [![gitguardian_logo.png](images/gitguardian_logo.jpeg)](https://blog.gitguardian.com/gitguardian-is-proud-sponsor-of-owasp/) [GitGuardian](https://www.gitguardian.com/) for their sponsorship which allows us to pay the bills for our cloud-accounts. [![JetBrains logo.](https://www.jetbrains.com/company/brand/img/logo_jb_dos_3.svg)](https://jb.gg/OpenSource) [Jetbrains](https://www.jetbrains.com/) for licensing an instance of Intellij IDEA Ultimate edition to the project leads. We could not have been this fast with the development without it! [![1password_logo.png](images/1password_logo.png)](https://github.com/1Password/1password-teams-open-source/pull/552) [1Password](https://1password.com/) for granting us an open source license to 1Password for the secret detection testbed. [![AWS Open Source](images/aws-white_48x29.png)](https://aws.amazon.com/) [AWS](https://aws.amazon.com/) for granting us AWS Open Source credits which we use to test our project and the [Wrongsecrets CTF Party](https://github.com/OWASP/wrongsecrets-ctf-party) setup on AWS. ## Help Wanted You can help us by the following methods: - Star us - Share this app with others - Of course, we can always use your help [to get more flavors](https://github.com/OWASP/wrongsecrets/issues/37) of "wrongly" configured secrets in to spread awareness! We would love to get some help with other cloud providers, like Alibaba or Tencent cloud for instance. Do you miss something else than a cloud provider? File an issue or create a PR! See [our guide on contributing for more details](CONTRIBUTING.md). Contributors will be listed in releases, in the "Special thanks & Contributors"-section, and the web-app. ## Use OWASP WrongSecrets as a secret detection benchmark As tons of secret detection tools are coming up for both Docker and Git, we are creating a Benchmark testbed for it. Want to know if your tool detects everything? We will keep track of the embedded secrets in [this issue](https://github.com/OWASP/wrongsecrets/issues/201) and have a [branch](https://github.com/OWASP/wrongsecrets/tree/experiment-bed) in which we put additional secrets for your tool to detect. The branch will contain a Docker container generation script using which you can eventually test your container secret scanning. ### Automated Secret Scanner Comparison We now provide an automated GitHub Action workflow that benchmarks multiple secret scanning tools against the WrongSecrets codebase. The [Secret Scanner Comparison workflow](/.github/workflows/scanner-comparison.yml) tests 7 different tools: - **TruffleHog** - Docker-based secret scanner - **git-secrets** - AWS Labs' git hook scanner - **gitleaks** - High-performance Go-based scanner - **detect-secrets** - Yelp's enterprise scanner - **gittyleaks** - Python-based pattern detector - **whispers** - Skyscanner's structured scanner - **trufflehog3** - Python version of TruffleHog The workflow runs weekly and provides a comparison table showing how many secrets each tool detects, helping you understand the relative effectiveness of different secret scanning tools. See [docs/scanner-comparison.md](/docs/scanner-comparison.md) for more details on running and interpreting the results. ## CTF We have 3 ways of playing CTFs: - The quick "let's play"-approach based on our own Heroku domain [https://wrongsecrets-ctf.herokuapp.com](https://wrongsecrets-ctf.herokuapp.com), which we documented for you here. - A more extended approach documented in [ctf-instructions.md](/ctf-instructions.md). - A fully customizable CTF setup where every player gets its own virtual instance of WrongSecrets and a virtual instance of the wrongsecrets-desktop, so they all can play hassle-free. For this you have to use [the WrongSecrets CTF Party setup](https://github.com/OWASP/wrongsecrets-ctf-party). ### CTFD Support Want to use CTFD to play a CTF based on the free Heroku wrongsecrets-ctf instance together with CTFD? You can! NOTE: CTFD support now works based on the [Juiceshop CTF CLI](https://github.com/juice-shop/juice-shop-ctf). NOTE-II: [https://wrongsecrets-ctf.herokuapp.com](https://wrongsecrets-ctf.herokuapp.com) (temporary down based on lack of oss credits) is based on Heroku and has limited capacity. Initial creation of the zip file for CTFD requires you to visit [https://wrongsecrets-ctf.herokuapp.com/api/Challenges](https://wrongsecrets-ctf.herokuapp.com/api/Challenges) once before executing the steps below. Follow the following steps: ```shell npm install -g juice-shop-ctf-cli@12.0.0 juice-shop-ctf #choose ctfd and https://wrongsecrets-ctf.herokuapp.com as domain. No trailing slash! The key is 'TRwzkRJnHOTckssAeyJbysWgP!Qc2T', feel free to enable hints. docker run -p 8001:8000 -it ctfd/ctfd:3.7.4 ``` > **Note:** Hints can only be generated if the WrongSecrets instance has hints enabled (`HINTS_ENABLED=true`). The Heroku CTF instance ([https://wrongsecrets-ctf.herokuapp.com](https://wrongsecrets-ctf.herokuapp.com)) runs with `HINTS_ENABLED=false`, so selecting "Free hints" or "Paid hints" will result in an empty hints list. To generate hints, run your own instance with `HINTS_ENABLED=true`. Now visit the CTFD instance at [http://localhost:8001](http://localhost:8001) and setup your CTF. Then use the administrative backup function to import the zipfile you created with the juice-shop-ctf command. Game on using [https://wrongsecrets-ctf.herokuapp.com](https://wrongsecrets-ctf.herokuapp.com)! Want to setup your own? You can! Watch out for people finding your key though, so secure it properly: make sure the running container with the actual ctf-key is not exposed to the audience, similar to our heroku container. ## FBCTF Support (Experimental!) NOTE: FBCTF support is experimental. Follow the same step as with CTFD, only now choose fbctfd and as a url for the countrymapping choose `https://raw.githubusercontent.com/OWASP/wrongsecrets/79a982558016c8ce70948a8106f9a2ee5b5b9eea/config/fbctf.yml`. Then follow [https://github.com/facebookarchive/fbctf/wiki/Quick-Setup-Guide](https://github.com/facebookarchive/fbctf/wiki/Quick-Setup-Guide) to run the FBCTF. ## Notes on development For development on local machine use the `local` profile `./mvnw spring-boot:run -Dspring-boot.run.profiles=local,without-vault` If you want to test against vault without K8s: start vault locally with ```shell export SPRING_CLOUD_VAULT_URI='http://127.0.0.1:8200' export VAULT_API_ADDR='http://127.0.0.1:8200' vault server -dev ``` and in your next terminal, do (with the token from the previous commands): ```shell export SPRING_CLOUD_VAULT_URI='http://127.0.0.1:8200' export SPRING_CLOUD_VAULT_TOKEN='<TOKENHERE>' vault token create -id="00000000-0000-0000-0000-000000000000" -policy="root" vault kv put secret/secret-challenge vaultpassword.password="$(openssl rand -base64 16)" vault kv put secret/injected vaultinjected.value="$(openssl rand -base64 16)" vault kv put secret/codified challenge47secret.value="debugvalue" ``` Now use the `local-vault` profile to do your development. ```shell ./mvnw spring-boot:run -Dspring-boot.run.profiles=local,local-vault ``` If you want to dev without a Vault instance, use additionally the `without-vault` profile to do your development: ```shell ./mvnw spring-boot:run -Dspring-boot.run.profiles=local,without-vault ``` Want to push a container? See `.github/scripts/docker-create-and-push.sh` for a script that generates and pushes all containers. Do not forget to rebuild the app before composing the container. Want to check why something in vault is not working in kubernetes? Do `kubectl exec vault-0 -n vault -- vault audit enable file file_path=stdout`. ### Dependency management We have CycloneDX and OWASP Dependency-check integrated to check dependencies for vulnerabilities. You can use the OWASP Dependency-checker by calling `mvn dependency-check:aggregate` and `mvn cyclonedx:makeBom` to use CycloneDX to create an SBOM. ### Dependency-Check Maven Plugin Configuration OWASP WrongSecrets uses the [`dependency-check-maven`](https://jeremylong.github.io/DependencyCheck/dependency-check-maven/index.html) plugin to automatically scan project dependencies for known vulnerabilities (CVEs). #### How It Works - The plugin runs during the Maven build (`./mvnw clean install`) and checks all dependencies against public vulnerability databases. - By default, it uses the NVD (National Vulnerability Database) and can also use OSS Index for additional coverage. #### Configuration Highlights The plugin is configured in `pom.xml` under the `<build><plugins>` section: ```xml <plugin> <groupId>org.owasp</groupId> <artifactId>dependency-check-maven</artifactId> <version>${dependency-check-maven.version}</version> <configuration> <nvdApiKey>...</nvdApiKey> <assemblyAnalyzerEnabled>false</assemblyAnalyzerEnabled> <ossIndexServerId>ossindex</ossIndexServerId> <ossIndexAnalyzerEnabled>true</ossIndexAnalyzerEnabled>  </configuration> <executions> <execution> <goals> <goal>check</goal> </goals> </execution> </executions> </plugin> ``` - **nvdApiKey**: API key for accessing the NVD database (recommended for faster and more reliable scans). - **ossIndexServerId**: References credentials in your Maven `settings.xml` for OSS Index (see below). - **ossIndexAnalyzerEnabled**: Set to `true` to enable OSS Index scanning. If you encounter authentication errors (401), set this to `false` to disable OSS Index. #### Authenticating with OSS Index To use OSS Index, you need to add your credentials to your Maven `settings.xml`: ```xml <servers> <server> <id>ossindex</id> <username>YOUR_OSSINDEX_USERNAME</username> <password>YOUR_OSSINDEX_API_TOKEN</password> </server> </servers> ``` Replace `YOUR_OSSINDEX_USERNAME` and `YOUR_OSSINDEX_API_TOKEN` with your OSS Index account details. #### Troubleshooting - If you see `401 Unauthorized` errors for OSS Index, check your credentials or disable OSS Index by setting `<ossIndexAnalyzerEnabled>false</ossIndexAnalyzerEnabled>` in `pom.xml`. - You can always run the build without OSS Index if you prefer only NVD-based scanning. #### More Info See [Dependency-Check Maven Plugin Documentation](https://jeremylong.github.io/DependencyCheck/dependency-check-maven/index.html) for advanced configuration options. ### Get the project started in IntelliJ IDEA Requirements: make sure you have the following tools installed: [Docker](https://www.docker.com/products/docker-desktop/), [Java26 JDK](https://jdk.java.net/26/), [NodeJS 26](https://nodejs.org/en/download/current) and [IntelliJ IDEA](https://www.jetbrains.com/idea/download). 1. Fork and clone the project as described in the [documentation](https://github.com/OWASP/wrongsecrets/blob/master/CONTRIBUTING.md). 2. Import the project in IntelliJ (e.g. import as mvn project / local sources) 3. Go to the project settings and make sure it uses Java26 (And that the JDK can be found) 4. Go to the IDE settings>Language & Frameworks > Lombok and make sure Lombok processing is enabled 5. Open the Maven Tab in your IDEA and run "Reload All Maven Projects" to make the system sync and download everything. Next, in that same tab use the "install" option as part of the OWASP WrongSecrets Lifecycle to genereate the asciidoc and such. 6. Now run the `main` method in `org.owasp.wrongsecrets.WrongSecretsApplication.java`. This should fail with a stack trace. 7. Now go to the run configuration of the app and make sure you have the active profile `without-vault`. This is done by setting the VM options arguments to `--server.port=8080 --spring.profiles.active=local,without-vault`. Set `K8S_ENV=docker` as environment argument. 8. Repeat step 6: run the app again, you should have a properly running application which is visitable in your browser at http://localhost:8080. **Pictorial Guide** on how to get the project started in IntelliJ IDEA is available at [_Contributing.md_](https://github.com/OWASP/wrongsecrets/blob/master/CONTRIBUTING.md#how-to-get-started-with-the-project-in-intellij-idea). Feel free to edit and propose changes via pull requests. Be sure to follow our guidance in the [documentation](https://github.com/OWASP/wrongsecrets/blob/master/CONTRIBUTING.md) to get your work accepted. Please note that we officially only support Linux and MacOS for development. If you want to develop using a Windows machine, use WSL2 or a virtual machine running Linux. We did include Windows detection & a bunch of `exe` files for a first experiment, but are looking for active maintainers of them. Want to make sure it runs on Windows? Create PRs ;-). If, after reading this section, you still have no clue on the application code: Have a look [at some tutorials on Spring boot from Baeldung](https://www.baeldung.com/spring-boot). ### Automatic reload during development To make changes made load faster we added `spring-dev-tools` to the Maven project. To enable this in IntelliJ automatically, make sure: - Under Compiler -> Automatically build project is enabled, and - Under Advanced settings -> Allow auto-make to start even if developed application is currently running. You can also manually invoke: Build -> Recompile the file you just changed, this will also force reloading of the application. ### How to add a Challenge Follow the steps below on adding a challenge: 1. First make sure that you have an [Issue](https://github.com/OWASP/wrongsecrets/issues) reported for which a challenge is really wanted. 2. Add the new challenge in the `org.owasp.wrongsecrets.challenges` folder. Make sure you add an explanation in `src/main/resources/explanations` and refer to it from your new Challenge class. 3. Add unit, integration and UI tests as appropriate to show that your challenge is working. 4. Do not forget to configure the challenge in `src/main/resources/wrong-secrets-configuration.yaml` 5. Review the [CONTRIBUTING guide](CONTRIBUTING.md) for setting up your contributing environment and writing good commit messages. For more details please refer [_Contributing.md_](https://github.com/OWASP/wrongsecrets/blob/master/CONTRIBUTING.md#how-to-add-a-challenge). If you want to move existing cloud challenges to another cloud: extend Challenge classes in the `org.owasp.wrongsecrets.challenges.cloud` package and make sure you add the required Terraform in a folder with the separate cloud identified. Make sure that the environment is added to `org.owasp.wrongsecrets.RuntimeEnvironment`. Collaborate with the others at the project to get your container running so you can test at the cloud account. ### Local testing If you have made some changes to the codebase or added a new challenge and would like to see exactly how the container will look after merge for testing, we have a script that makes this very easy. Follow the steps below: 1. Ensure you have bash installed and open. 2. Navigate to .github/scripts. 3. Run the docker-create script `bash docker-create.sh`. - Note: Do you want to run this on your minikube? then first run `eval $(minikube docker-env)`. 4. Follow any instructions given, you made need to install/change packages. 5. Run the newly created container: - to running locally: `docker run -p 8080:8080 -p 8090:8090 jeroenwillemsen/wrongsecrets:local-test-no-vault` - to run it on your minikube: use the container `jeroenwillemsen/wrongsecrets:local-test-k8s-vault` in your deployment definition. - to run it with Vault on your minikube: use the container `jeroenwillemsen/wrongsecrets:local-test-local-vault` in your deployment definition. ### Local Automated testing We currently have 2 different test-suites, both fired with `./mvnw test`. - A normal junit test suite of unit and integration tests, located at the [`test/java` folder](src/test/java) with output stored at the default target directory. - A cypress test suite, integrated by means of a junit test, located at [`test/e2e` folder](src/test/e2e) with output stored at [`target/test-classes/e2e/cypress/reports/`](target/test-classes/e2e/cypress/reports/). See the [cypress readme](src/test/e2e/cypress/README.md) for more details. Note: You can do a full roundtrip of cleaning, building, and testing with `./mvnw clean install`. ## 🔧 Troubleshooting ### Common Issues **Docker Issues:** - **Port already in use**: Change the port mapping: `docker run -p 8081:8080 -p 8091:8090 jeroenwillemsen/wrongsecrets:latest-no-vault` - **Docker not found**: Make sure Docker is installed and running - **Permission denied**: On Linux, you might need to add your user to the docker group **Browser Issues:** - **Can't access localhost:8080**: Check if Docker container is running with `docker ps` - **Challenges not loading**: Clear browser cache or try incognito mode **Kubernetes Issues:** - **Minikube won't start**: Try `minikube delete` then `minikube start` - **Pods stuck in pending**: Check resources with `kubectl describe pod <pod-name>` **Need Help?** - Check our [GitHub Issues](https://github.com/OWASP/wrongsecrets/issues) - Join us on [OWASP Slack](https://owasp.slack.com/archives/C02KQ7D9XHR) - Review the [Support](#support) section ## Want to play, but are not allowed to install the tools? If you want to play the challenges, but cannot install tools like keepass, Radare, etc. But are allowed to run Docker containers, try the following: ```shell docker run -p 3000:3000 -v /var/run/docker.sock:/var/run/docker.sock jeroenwillemsen/wrongsecrets-desktop:latest ``` or use something more configurable: ```shell docker run -d \ --name=webtop \ --security-opt seccomp=unconfined \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Europe/London \ -e SUBFOLDER=/ \ -e KEYBOARD=en-us-qwerty \ -p 3000:3000 \ -v /var/run/docker.sock:/var/run/docker.sock \ --shm-size="2gb" \ --restart unless-stopped \ jeroenwillemsen/wrongsecrets-desktop:latest ``` And then at [http://localhost:3000](http://localhost:3000). Note: be careful with trying to deploy the `jeroenwillemsen/wrongsecrets-desktop` container to Heroku ;-). ## Docker on macOS with M1 and Colima (Experimental!) NOTE: We do not officially support Colima, as we can tell that Github runners have loads of issues with it. If you cannot switch to Docker Desktop/Podman and you want to use Colima with Apple Silicon M1 to run Docker image `jeroenwillemsen/wrongsecrets` you try one of: - switch off Colima (`colima stop`) - change Docker context (`docker --context desktop-linux run -p 8080:8080 jeroenwillemsen/wrongsecrets:latest-no-vault`) - run Colima with 1 CPU (`colima start -m 8 -c 1 --arch x86_64`) ## Want to disable challenges in your own release? If you want to run WrongSecrets but without certain challenges you don't want to present to others: please read this section. *_NOTE_* Please note that we do not deliver any support to your fork when you follow the process below. Please understand that license and copyright of the original application remain intact for your Fork. Requirements: - Have the JDK of Java 26 installed; - Have an account at a registry to which you can push your variant of the WrongSecrets container; Here are the steps you have to follow to create your own release of WrongSecrets with certain challenges disabled: 1. Fork the repository. 2. In `src/main/resources/wrong-secrets-configuration.yaml` remove the reference to the challenge you no longer want to have in your fork. 3. In the root of the project run `./mvnw clean install` 4. Now build the Docker image for your target of choice: ```sh docker buildx create --name mybuilder docker buildx use mybuilder docker buildx build --platform linux/amd64,linux/arm64 -t <registry/container-name>:<yourtag>-no-vault --build-arg "argBasedPassword='this is on your command line'" --build-arg "PORT=8081" --build-arg "argBasedVersion=<yourtag>" --build-arg "spring_profile=without-vault" --push . docker buildx build --platform linux/amd64,linux/arm64 -t <registry/container-name>:<yourtag>-kubernetes-vault --build-arg "argBasedPassword='this is on your command line'" --build-arg "PORT=8081" --build-arg "argBasedVersion=<yourtag>" --build-arg "spring_profile=kubernetes-vault" --push . ``` ## Further reading on secrets management Want to learn more? Checkout the sources below: - [Blog: 10 Pointers on Secrets Management](https://dev.to/commjoen/secure-deployment-10-pointers-on-secrets-management-187j) - [OWASP SAMM on Secret Management](https://owaspsamm.org/model/implementation/secure-deployment/stream-b/) - [The secret detection topic at Github](https://github.com/topics/secrets-detection) - [OWASP Secretsmanagement Cheatsheet](https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Secrets_Management_Cheat_Sheet.md) - [OpenCRE on secrets management](https://www.opencre.org/cre/223-780?register=true&type=tool&tool_type=training&tags=secrets,training&description=With%20this%20app%2C%20we%20have%20packed%20various%20ways%20of%20how%20to%20not%20store%20your%20secrets.%20These%20can%20help%20you%20to%20realize%20whether%20your%20secret%20management%20is%20ok.%20The%20challenge%20is%20to%20find%20all%20the%20different%20secrets%20by%20means%20of%20various%20tools%20and%20techniques.%20Can%20you%20solve%20all%20the%2067%20challenges%3F&trk=flagship-messaging-web&messageThreadUrn=urn:li:messagingThread:2-YmRkNjRkZTMtNjRlYS00OWNiLWI2YmUtMDYwNzY3ZjI1MDcyXzAxMg==&lipi=urn:li:page:d_flagship3_feed;J58Sgd80TdanpKWFMH6z+w==)

Carregando o README do repositório…

Skills neste repositório

Administradores de redes e sistemas de computador

1 categorias ocupacionais · 100% classificado

skill

ocupação

descrição

atualizado

deploy-preview

Administradores de redes e sistemas de computador

Deploy the branch that is currently checked out to the shared staging preview environment and report the preview URL back to the user.

Idioma do texto original: inglês

2026-09-08

Mostrando 1 de 1 skills coletadas.