Drag the line to compare scanner output with the report. Self-owned, isolated lab example; no live credential.
finding-demo-01 — A file containing a GitHub token was publicly reachable at http://lab-vuln-variety:8090/marker/exposed-github-token.
Customer risk: High · Source severity: High
What we found
A file containing a GitHub token was publicly reachable at http://lab-vuln-variety:8090/marker/exposed-github-token.
Assessment boundary
Discovered credential material is not used to authenticate or test account access. Self-owned isolated lab example; no live credential.
Why it matters
A publicly reachable credential file can expose access to connected services. This demonstration uses a non-live lab placeholder; credential usability was not tested.
Finding category
Secrets and credential exposure — Credential material returned without authentication.
Known causes
Deployment artifacts containing credentials placed under the web root.
Likelihood
High
Impact
Medium
Technical assessment
High — Illustrative lab assessment
Contextual proposal
High
Final result
High
CVSS
Not scored
Severity rationale
Illustrative High rating for exposed credential-pattern content. Actual impact depends on privileges and asset context; no credential was used to authenticate.
HTTP/1.1 200 OK
ghp_labonlynotreal000000000000000000000
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.