A security research diagram mapping attack paths to exploit GitHub Actions misconfigurations for red team engagements.
GitHub Actions Attack Diagram is a security research project that provides a visual guide to identifying and exploiting vulnerabilities in GitHub Actions workflows. It outlines attack paths from initial access to critical compromises like self-hosted runner takeover and secrets exfiltration, based on real-world red team engagements. The diagram helps security professionals understand and test for misconfigurations in CI/CD pipelines.
Security researchers, red teamers, penetration testers, and DevOps engineers focused on securing GitHub Actions workflows and CI/CD pipelines.
It offers a concise, field-tested map of attack techniques derived from actual exploits, presented at top security conferences, making it a practical resource for offensive security assessments.
The GitHub Actions Attack Diagram is a security research artifact that provides structured guidance for identifying and exploiting vulnerabilities in GitHub Actions workflows. It maps attack paths from initial access to critical outcomes like self-hosted runner takeover and secrets exfiltration, based on real-world red team engagements and public vulnerability research presented at major security conferences.
The diagram focuses on practical, field-tested attack paths rather than being an exhaustive list, emphasizing actionable guidance for security professionals.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Visualizes common TTPs from initial access to critical compromises like self-hosted runner takeover and secrets exfiltration, based on real-world red team engagements.
Derived from actual exploits presented at Black Hat USA 2024 and DEF CON 32, ensuring practical, field-tested techniques.
Includes references to detailed slides, talks, and blog posts with real examples like supply chain attacks on PyTorch and Microsoft.
Encourages contributions via Issues to adapt to GitHub's evolving configurations, helping keep the diagram current.
The diagram admits it's not inclusive, focusing only on major attack paths used in live environments, which may miss emerging vulnerabilities.
It's a visual guide, not an automated tool, so users must manually analyze and apply techniques, which can be time-consuming.
Primarily geared towards exploitation, with minimal advice on prevention or remediation, limiting its use for defensive teams.