PR: OIDC Connection Detection in GitHub Actions Workflows#91
Open
DS-KoolAid wants to merge 4 commits intomainfrom
Open
PR: OIDC Connection Detection in GitHub Actions Workflows#91DS-KoolAid wants to merge 4 commits intomainfrom
DS-KoolAid wants to merge 4 commits intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've added detection for OIDC connections in GitHub Actions workflows. This helps us find when workflows are authenticating to cloud providers using GitHub's OIDC provider.
What's in this PR
The main feature is a new method in the
WorkflowParserclass that scans workflows for OIDC connections to cloud providers. It detects:aws-actions/configure-aws-credentials@v2and env vars likeAWS_ROLE_ARNgoogle-github-actions/authazure/loginand related client/tenant IDsvault-actionWhy this matters
Workflows with OIDC can access sensitive cloud resources. For pen testing, these are potential privilege escalation paths.
Example output:
