finding-demo-01 — A file containing a GitHub token was publicly reachable at http://lab-vuln-variety:8090/marker/exposed-github-token.
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
How to fix
- Remove the exposed file from the public web path serving /marker/exposed-github-token.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.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.Re-run the Nuclei template and verify the file is no longer publicly reachable.
Category remediation playbook
Category remediation playbook
- Immediately revoke and rotate every exposed credential, key, and token; treat exposure as compromise until proven otherwise.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.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.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.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.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.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
Example fix
location = /marker/exposed-github-token { deny all; }location = /marker/exposed-github-token { deny all; }Technical references
Technical references
- OWASP Secrets Management Cheat Sheet — Guidance for managing and rotating secrets.https://cheatsheetseries.owasp.org/cheatsheets/Secrets_Management_Cheat_Sheet.htmlOWASP Secrets Management Cheat Sheet — Guidance for managing and rotating secrets.https://cheatsheetseries.owasp.org/cheatsheets/Secrets_Management_Cheat_Sheet.html
Security references
Security references
Evidence screenshot
Evidence screenshot
Historical synthetic lab capture retained to demonstrate the evidence view. No live credential or customer data.
Historical synthetic lab capture retained to demonstrate the evidence view. No live credential or customer data.
Capture hash: 9ff529f1ad4a5c2652d96b7dd9e7c1d6d7681eeaab06faa7ddd15e9fe07ac686
Capture hash: 221e501f276b4ab4f8b78e44fdbda29d36cceff8a41f2c2593ea2624b1023c95
Finding evidence binding: Not issued for this website illustration.
Finding evidence binding: Not issued for this website illustration.
Screenshot render binding: Not issued for this website illustration.
Screenshot render binding: Not issued for this website illustration.