-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add pull_request_target event to GitHub workflows #941
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Critical Security Issue: Unsafe pull_request_target implementation detected
The workflows are using
pull_request_target
trigger while checking out code and accessing sensitive repository secrets (AWS credentials) without explicitly specifying the base ref. This creates a security vulnerability where malicious PR code could potentially access production AWS credentials.Current security issues:
actions/checkout@v4
without specifyingref
Required fixes:
pull_request_target
trigger as it's unnecessary (workflows already havepull_request
trigger)pull_request_target
must be kept, addref: ${{ github.event.pull_request.base.ref }}
to checkout actionpull_request
trigger for building/testing PR codepull_request_target
for tasks requiring secrets🔗 Analysis chain
Security Warning: Carefully review pull_request_target implementation
Adding
pull_request_target
trigger requires careful consideration as it runs with repository context and has access to secrets, even from fork PRs. This can be dangerous if the workflow checks out and runs untrusted PR code with access to secrets.To ensure security:
ref: ${{ github.event.pull_request.base.ref }}
)Let's verify the checkout configuration:
Let me check the complete workflow file content to verify the checkout configuration and job permissions:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 983
Script:
Length of output: 5790