IntegrityLab.ai
Sample finding · Exposed credential fileUnredacted / Redacted report

Yellow: full · Green: redacted. Outlined areas show what changes.

Unredacted Redacted

One finding. Two audiences.

Current individual-finding template, populated with illustrative self-owned isolated lab data. Historical screenshot pair. No live credentials, customer data, or current signed assessment.

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.

Customer risk: High · Source severity: High

Customer risk: High · Source severity: High

What we found
What we found
A file containing a GitHub token was publicly reachable at http://lab-vuln-variety:8090/marker/exposed-github-token.
A file containing a GitHub token was publicly reachable at http://lab-vuln-variety:8090/marker/exposed-github-token.
Assessment boundary
Assessment boundary
Discovered credential material is not used to authenticate or test account access. Self-owned isolated lab example; no live credential.
Discovered credential material is not used to authenticate or test account access. Self-owned isolated lab example; no live credential.
Why it matters
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.
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
Finding category
Secrets and credential exposure — Credential material returned without authentication.
Secrets and credential exposure — Credential material returned without authentication.
Known causes
Known causes
  • Deployment artifacts containing credentials placed under the web root.
    Deployment artifacts containing credentials placed under the web root.
Likelihood
Likelihood
High
High
Impact
Impact
Medium
Medium
Technical assessment
Technical assessment
High — Illustrative lab assessment
High — Illustrative lab assessment
Contextual proposal
Contextual proposal
High
High
Final result
Final result
High
High
CVSS
CVSS
Not scored
Not scored
Severity rationale
Severity rationale
Illustrative High rating for exposed credential-pattern content. Actual impact depends on privileges and asset context; no credential was used to authenticate.
Illustrative High rating for exposed credential-pattern content. Actual impact depends on privileges and asset context; no credential was used to authenticate.
Target
Target
http://lab-vuln-variety:8090/marker/exposed-github-token
http://lab-vuln-variety:8090/marker/exposed-github-token
Tools
Tools
Nuclei · credential-pattern inspection (illustrative lab example)
Nuclei · credential-pattern inspection (illustrative lab example)
Reproduction command
Reproduction command
[Redacted for delivery]
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
Observed output summary
[Redacted for delivery]
HTTP/1.1 200 OK
ghp_labonlynotreal000000000000000000000
How to fix
How to fix
  1. 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.
  2. Store configuration and secrets outside the document root with least-privilege access.
    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.
    Re-run the Nuclei template and verify the file is no longer publicly reachable.
Category remediation playbook
Category remediation playbook
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  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.
    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; }

Illustrative configuration; adapt and validate for your stack.

Illustrative configuration; adapt and validate for your stack.

Technical references
Technical references
Security references
Security references
CWE
CWE
CWE-522 (https://cwe.mitre.org/data/definitions/522.html)
CWE-522 (https://cwe.mitre.org/data/definitions/522.html)
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.

Capture for finding-demo-01
Capture for finding-demo-01