finding-demo-01 — A file containing a GitHub token was publicly reachable at http://lab-vuln-variety:8090/marker/exposed-github-token.
How to fix
- Remove the exposed file from the public web path serving /marker/exposed-github-token.
- Store configuration and secrets outside the document root with least-privilege access.
- Re-run the Nuclei template and verify the file is no longer publicly reachable.
Category remediation playbook
- Immediately revoke and rotate every exposed credential, key, and token; treat exposure as compromise until proven otherwise.
- Remove the exposed artifact from the public surface and from any CDN/object-store cache.
- Move secrets to a secrets manager or environment injection path that is never served as static content.
- Add fail-closed access controls (authn + network allowlists) on any path that can return configuration.
- Scan repositories and deploy packages for residual secret material; block future commits with secret scanning.
- Re-run the exposure check to confirm the path is no longer publicly accessible. The asset owner should manage credential rotation; this assessment does not use discovered credentials to authenticate.
Example fix
location = /marker/exposed-github-token { deny all; }
Technical references
- OWASP Secrets Management Cheat Sheet — Guidance for managing and rotating secrets.https://cheatsheetseries.owasp.org/cheatsheets/Secrets_Management_Cheat_Sheet.html
Security references
Evidence screenshot
Historical synthetic lab capture retained to demonstrate the evidence view. No live credential or customer data.
Capture hash: Historical lab illustration; not a current signed evidence hash
Finding evidence binding:
Screenshot render binding: