TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Compromising GitHub Repositories Through the Actions Dependency Tree

2 pointsby jdwgover 1 year ago

1 comment

jeplerover 1 year ago
my tldr:<p>If an action was originally at org1&#x2F;name1 but was transferred to org2&#x2F;name2, git operations using org1&#x2F;name1 (including fetching actions) continue to work, silently redirected to org2&#x2F;name2.<p>This is true right up until org1&#x2F;name1 is created again, at which time the redirect is removed.<p>This allows a (potentially new!) org1 to upload whatever they like and replace the action. It doesn&#x27;t matter if you trusted org1 &quot;back then&quot; and trust org2 now, new-org1 gets to determine what is in your action.<p>Because transitive dependency graphs are so sprawling, you might just be vulnerable to this.<p>Using actions &quot;@hex-ref&quot; may help with this somewhat but it&#x27;s not a magic bullet and has its own downsides.<p>Yet another reason to write dumb github actions (e.g., that avoid doing anything more sophisticated than run shell commands), imo.