The GitHub Actions Attack Diagram provides guidance for identifying GitHub Actions vulnerabilities. Starting with read-only or write access to a GitHub organization/repository, you can follow the diagram to determine how to identify and exploit GitHub Actions misconfigurations, from self-hosted runner takeover, to PWN requests, to secrets exfiltration. Throughout the diagram, various resources are linked to provide additional context.

The diagram outlines common attack paths Adnan Khan and I have used on Red Team engagements and during public vulnerability research. We presented this research in-depth at Black Hat USA 2024 (Continuous Integration, Continuous Desctruction, slides) and DEF CON 32 (Grand Theft Actions, slides).

These attack paths may change over time as GitHub updates their internal configurations. If you notice that certain TTPs are no longer valid or to request the addition of new TTPs, please create an Issue, and I'll add you to the Contributors list.

This diagram is not inclusive, rather, it outlines major attack paths and TTPs we have used on targets in live environments.

Enjoy:)

If you're curious about how we've used these TTPs to exploit critical CI/CD vulnerabilities in the wild, you can check out our BH/DC talks linked above, or read some of the following blog posts we've released.

• Playing With Fire - How We Executed a Critical Supply Chain Attack on PyTorch
• Fixing Typos and Breaching Microsoft's Perimeter
• One Supply Chain Attack to Rule Them All
• RoguePuppet
• AStar Network Supply Chain Attack
• Worse Than Solarwinds - Three Steps to Hack Blockchains, GitHub, and ML Through GitHub Actions
• TensorFlow Supply Chain Compromise via Self-Hosted Runner Attack
• Compromising ByteDance’s Rspack using GitHub Actions Vulnerabilities