Repository navigation
Title: [Security research — do not merge] Verify Cocoon autosubmit allowlist behavior - #1
Open
auto-submit wants to merge 1 commit into
Open
auto-submit wants to merge 1 commit into
auto-submit wants to merge 1 commit into
Conversation
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
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.
This PR is part of a coordinated security test requested by the Google Bug Hunter
team on issuetracker.google.com/issues/573492605.
The report concerns
flutter/.github's autosubmit.yml allowlist, which includesthe bare username "auto-submit" (not "auto-submit[bot]") in auto_approval_accounts.
This account is a newly-registered test account with that exact name, created to
verify whether Cocoon's approval.dart treats it as a trusted roller account.
Could a maintainer with the appropriate permission apply the
autosubmitlabel tothis PR so we can observe Cocoon's behavior? This PR's change is a trivial doc typo
fix and is safe to merge or close either way. I will close this PR immediately
once the behavior is confirmed, regardless of outcome.
cc: Google Bug Hunter Team (ref: 573492605)