Skip to content

[static-analysis] RGS-012: Secret Exfiltration via Outbound HTTP Request in visual-regression-checker.lock.ymlΒ #54157

Closed as not planned

Description

@github-actions

🚨 Runner-Guard Security Finding

Rule: RGS-012 β€” Secret Exfiltration via Outbound HTTP Request
Severity: High
File: .github/workflows/visual-regression-checker.lock.yml
Line: 846 β€” step "Execute GitHub Copilot CLI"

Description

Runner-Guard flagged a run:-adjacent block containing an outbound HTTP request targeting a non-GitHub domain in a job context with secrets/publishing access, a pattern generally associated with credential exfiltration.

Impact

If a job triggered by an untrusted event makes an outbound request carrying secrets to an attacker-controlled domain, it can exfiltrate CI credentials.

Investigation notes (manual review before this run)

The flagged line is a comment listing the Copilot CLI's allowed tool invocations, not executable exfiltration code:

# Copilot CLI tool arguments (sorted):
# --allow-tool shell(curl (host.docker.internal/redacted)
# --allow-tool shell(curl (localhost/redacted)

Both targets (host.docker.internal and localhost) are loopback/local-network addresses used to let the agent curl a local dev server (consistent with a visual-regression workflow that screenshots a locally-running app), not an external domain capable of receiving exfiltrated secrets. This looks like a likely false positive: the non-GitHub-domain heuristic doesn't currently special-case loopback/link-local addresses.

Remediation

  • If confirmed as a false positive, consider excluding loopback addresses (localhost, 127.0.0.1, host.docker.internal) from the "non-GitHub domain" exfiltration heuristic, or suppress this specific rule for comment-only lines (# --allow-tool ...) rather than executable run: content.
  • Re-verify that no other step in this workflow actually issues an outbound curl to host.docker.internal/localhost carrying secret values as payload β€” the allow-list only bounds what the agent may call, not proof of what it does call.

Detected by runner-guard v2.6.0 β€” CI/CD source-to-sink vulnerability scanner
Workflow run: https://github.com/github/gh-aw/actions/runs/32333348563

Generated by πŸ“Š Static Analysis Report Β· agent Β· 197.9 AIC Β· βŒ– 9.57 AIC Β· ⊞ 11.5K Β· β—·

  • expires on Aug 26, 2026, 9:22 PM UTC-08:00

Activity

  1. github-actions commented on Aug 20, 2026

    @github-actions
    ContributorAuthor

    πŸͺ Issue Monster selected this for Copilot

    I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

    If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! πŸͺ

    πŸͺ Om nom nom by Issue Monster Β· gpt54 Β· 9.63 AIC Β· βŒ– 9.44 AIC Β· ⊞ 13.2K Β· β—·

  2. github-actions commented on Aug 21, 2026

    @github-actions
    ContributorAuthor

    πŸ”„ Recurring Finding β€” 2026-08-21

    This finding was detected again in today's static analysis scan.

    Workflow run: https://github.com/github/gh-aw/actions/runs/32448392658
    File: .github/workflows/visual-regression-checker.lock.yml
    Line: 879

    Same pattern as previously investigated: the flagged line is a comment listing the Copilot CLI's allowed tool invocations (--allow-tool shell(curl (host.docker.internal/... / localhost/...), not executable exfiltration code β€” both targets are loopback/local-network addresses. This remains a likely false positive in the non-GitHub-domain heuristic (it doesn't special-case loopback/link-local addresses yet).

    This issue remains open. Consider applying the remediation already proposed here (exclude loopback addresses from the heuristic, or suppress the rule for comment-only lines) to stop the recurring alerts.

    Generated by πŸ“Š Static Analysis Report Β· agent Β· 152.2 AIC Β· βŒ– 14.2 AIC Β· ⊞ 11.5K Β· β—·

  3. github-actions commented on Aug 21, 2026

    @github-actions
    ContributorAuthor

    This issue is being closed as outdated. A newer issue has been created: #54435

    View newer issue


    This action was performed automatically by the Static Analysis Report workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions