Repository navigation
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.
Preserve newer trusted base config during agent restoration #68817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Preserve newer trusted base config during agent restoration #68817
Changes from all commits
f6015cc3bd06a9127b839File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/diagnosing-bugs] 🔴 Critical:
git rev-parse --verify "refs/remotes/origin/${DEFAULT_BRANCH}^{commit}"does not do an exact-path ref lookup — it falls back through git's standard ref search order (includingrefs/heads/<name>). This reopens the exact attack this PR is meant to close.💡 Exploit and fix
A fork PR can name its branch
refs/remotes/origin/main.git checkout -B <headRef> origin/pr-headthen creates a local branch literally atrefs/heads/refs/remotes/origin/main. When the workspace has no realrefs/remotes/origin/<default>(e.g.pull_requestruns whereactions/checkoutonly fetchedrefs/pull/N/merge, or the PR base isn't the default branch),rev-parseresolvesBASE_SHAto the attacker's commit, which equalsHEAD_SHA— soFOLDERS/ROOT_FILESare emptied and restoration is skipped, leaving attacker-controlled.github/,.claude/, skills, andAGENTS.mdin place.I reproduced this locally: creating a branch named
refs/remotes/origin/mainand checking it out causes the current script to treat the attacker commit as the trusted base and skip restoration.Fix: replace the
rev-parsecall with an exact-path lookup that can't fall back to other namespaces:BASE_SHA=$(git -C "${WORKSPACE}" show-ref --verify --hash "refs/remotes/origin/${DEFAULT_BRANCH}" 2>/dev/null)I verified this rejects the attacker-branch scenario (exits non-zero, no match) while still resolving a genuine remote-tracking ref. Please add a regression test for this exact scenario (PR head named
refs/remotes/origin/<default-branch>) alongside the existing table-driven cases inpr_test.go.@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.