IntegrityLab.ai

IntegrityLab.ai sample finding · Self-owned isolated lab illustration · variant: customer · generated Historical example · current template

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.
Target
http://lab-vuln-variety:8090/marker/exposed-github-token
Tools
Nuclei · credential-pattern inspection (illustrative lab example)
Reproduction command
curl -X 'GET' -H 'Accept: */*' -H 'Accept-Language: en' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36' 'http://lab-vuln-variety:8090/marker/exposed-github-token'
Observed output summary
HTTP/1.1 200 OK
ghp_labonlynotreal000000000000000000000

How to fix

  1. Remove the exposed file from the public web path serving /marker/exposed-github-token.
  2. Store configuration and secrets outside the document root with least-privilege access.
  3. Re-run the Nuclei template and verify the file is no longer publicly reachable.

Category remediation playbook

  1. Immediately revoke and rotate every exposed credential, key, and token; treat exposure as compromise until proven otherwise.
  2. Remove the exposed artifact from the public surface and from any CDN/object-store cache.
  3. Move secrets to a secrets manager or environment injection path that is never served as static content.
  4. Add fail-closed access controls (authn + network allowlists) on any path that can return configuration.
  5. Scan repositories and deploy packages for residual secret material; block future commits with secret scanning.
  6. 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; }

Illustrative configuration; adapt and validate for your stack.

Technical references

Security references

CWE
CWE-522 (https://cwe.mitre.org/data/definitions/522.html)

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:

Full-size capture

Capture for finding-demo-01