Skip to content

Security research: verify CI secret exposure to fork PRs (non-exfiltrating length check) - #126

Closed
titsecop wants to merge 1 commit into
goshippo:mainfrom
titsecop:poc-token-length-check-v2
Closed

titsecop wants to merge 1 commit into
goshippo:mainfrom
titsecop:poc-token-length-check-v2

Conversation

@titsecop

Copy link
Copy Markdown

Authorized security research (HackerOne bug bounty program). This PR adds a single, non-exfiltrating line to the existing install-ci Makefile target that prints only the length of SHIPPO_TOKEN (never its value) to the CI log, to verify whether the repository secret configured in .github/workflows/sdk_validation.yaml (job-level env: SHIPPO_TOKEN: ${{ secrets.SHIPPO_TOKEN }}, triggered on pull_request with no org-membership gate) actually reaches a fork-submitted PR's CI run.

No secret value is printed, logged, or transmitted anywhere. This PR will be closed immediately after the CI result is observed. Happy to answer any questions — reachable via HackerOne.

… CI (length-only check via existing install-ci target, no exfiltration)
@titsecop

Copy link
Copy Markdown
Author

Closing — got the result I needed (workflow run status: action_required, confirming this repo requires maintainer approval for first-time-contributor PRs before secrets-bearing jobs execute). No further action needed on this PR. Thanks for your time.

@titsecop titsecop closed this Sep 14, 2026
@titsecop
titsecop deleted the poc-token-length-check-v2 branch September 14, 2026 03:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant