IBB security verification: CI execution context of fork-PR jobs (names-only recon, will close) - #40032
Closed
athulk-star wants to merge 1 commit into
Closed
IBB security verification: CI execution context of fork-PR jobs (names-only recon, will close)#40032athulk-star wants to merge 1 commit into
athulk-star wants to merge 1 commit into
Conversation
Author
|
Verification complete — recon output captured (env names only, metadata status codes, no secret values accessed). Closing as promised. Report to follow via IBB. Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Security verification PR under the Internet Bug Bounty (apache/beam is in scope).
What this does: adds a pytest conftest that prints, to the public job log only: environment variable NAMES (no values), path-existence booleans for the kubelet gcloud volume, and metadata-service HTTP status codes. No secret values are printed, nothing is exfiltrated, no repo state is modified by the check.
Why: the pull_request_target PreCommit workflows run fork-PR code on self-hosted runners with workflow-level env (DEVELOCITY/GE_CACHE credential NAMES visible) and a kubelet gcloud config path. This PR confirms which of those are present in the untrusted execution context so the exposure can be reported accurately.
Will be closed immediately after the job log is captured. Apologies for the noise, and thank you!