wrdn-gha-workflows

Detect exploitable GitHub Actions workflow vulnerabilities and map attacker-controlled paths.

6|1|Updated Nov 23, 2023
One-click install
npx skills add https://github.com/gmcabrita/dotfiles --skill wrdn-gha-workflows-gmcabrita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrdn-gha-workflows
Source: https://github.com/gmcabrita/dotfiles/tree/main/.agents/skills/wrdn-gha-workflows
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill wrdn-gha-workflows-gmcabrita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects exploitable GitHub Actions workflow vulnerabilities, including privileged PR contexts, unsafe input handling, and exposure of secrets.

Core Features & Use Cases

  • Trace entry points from triggers to sinks across .github/workflows, action.yml, reusable workflows, local actions, and scripts.
  • Identify expression-injection, pwn-request patterns, TOCTOU issues, and secret exposure with remediation guidance.
  • Use in code reviews to audit CI/CD workflows and prerun protections, and to validate workflow_call and workflow_dispatch inputs.

Quick Start

Scan a repository's workflows to generate an actionable report highlighting exploitable patterns and recommended mitigations.

Frequently Asked Questions about wrdn-gha-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find exploitable GitHub Actions workflow vulnerabilities in my code?

To find exploitable GitHub Actions workflow vulnerabilities, trace entry points from triggers to sinks across .github/workflows and action.yml files. This identifies expression-injection, pwn-request patterns, and unsafe input handling with structured remediation guidance.

What is a pwn-request pattern in GitHub Actions and how does it expose secrets?

A pwn-request pattern in GitHub Actions occurs when privileged PR contexts process untrusted input from forks, exposing secrets. Analyzing triggers and token scopes maps attacker-controlled paths to detect these expression-injection and TOCTOU risks.

How do I audit GitHub Actions workflow_call and workflow_dispatch inputs for unsafe input handling?

Audit GitHub Actions workflow_call and workflow_dispatch inputs by validating unsafe input handling and tracking entry points to sinks. Apply this to diffs touching reusable workflows, local actions, and scripts to map attacker-controlled paths.

Does this workflow security audit cover reusable workflows and local actions?

Yes, this workflow security audit covers reusable workflows and local actions. It tracks entry points, inputs, sinks, and token scopes across .github/workflows, action.yaml, scripts, and artifacts to output structured findings with remediation guidance.

What's the best way to detect TOCTOU issues and expression-injection in GitHub Actions workflows?

The best way to detect TOCTOU issues and expression-injection in GitHub Actions workflows is to trace untrusted inputs from triggers to sinks. Mapping privileged PR contexts and secret scopes reveals exploitable patterns for targeted remediation.

When do I need to scan .github/workflows for privileged PR contexts and token scopes?

Scan .github/workflows for privileged PR contexts and token scopes during code reviews or when diffs touch CI/CD workflows. This validates prerun protections and identifies exposure of secrets before merging changes.