advanced-bugbounty-mcp

The primary security risk is mounting `/var/run/docker.sock` into the `mcp-server` container (`bugbounty-mcp`), granting the container root access to the Docker host if the application inside is compromised (e.g., via command injection through an MCP tool call). This is a critical vulnerability. Additionally, MongoDB and Redis services have default hardcoded passwords (`bugbounty_secure_pass`, `bugbounty_redis`) that are used if environment variables are not explicitly set, and these services are exposed via `ports:` mappings in `docker-compose.yml` without explicit host firewall rules to restrict access to them in all deployment scenarios (e.g., `cloud-deploy.sh` only explicitly opens 8080/tcp, not implicitly blocking 27017/6379). The `curl | bash` installation method, while common, also presents a supply chain risk.