-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): bump the actions group across 1 directory with 10 updates #43
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
Closed
Closed
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 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
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
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
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
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.
🔒 Security & Privacy | 🛡️ Analyzed with Security Review | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: ultimaterex/fireproxy
Length of output: 5781
🌐 Web query:
actions checkout v4 v7 persist-credentials default GitHub token pull_request fork permissions💡 Result:
<search_synthesis>
In actions/checkout, the persist-credentials input governs whether the authentication token (or SSH key) is configured in the local git config [1][2]. Key details regarding persist-credentials and recent security updates: Default Behavior: The default value for persist-credentials is true across both v4 and v7 [2][3][4]. When enabled, this allows your workflow scripts to run authenticated git commands (e.g., git push) [1][4]. Security Enhancement: While it remains enabled by default, newer versions (specifically v6 and v7) have improved security by persisting these credentials in a separate file under the runner&
#39;s temporary directory ($RUNNER_TEMP) rather than directly within the.git/config file, reducing the risk of accidental exposure [4][5][6]. Fork Permissions and pull_request_target: In v7, actions/checkout introduced a significant security change for workflows triggered by pull_request_target and workflow_run events [7]. To prevent common "pwn request" attacks, v7 now refuses to fetch fork pull request code in these specific event types [7]. This restriction applies when the checkout attempts to access the fork's head or merge commit [7]. If a workflow specifically requires this behavior and has been reviewed for security, you can opt out of this protection by using the allow-unsafe-pr-checkout input [7]. In summary, persist-credentials defaults to true to maintain functionality for authenticated git operations, while v7 adds strict protections against fetching potentially malicious code from forks in privileged event contexts [7][4].</search_synthesis>
<source_evidence>
Citations:
Sensitive Data Exposure
Reachability: External
Exploitability: Trivial
CWE: CWE-522 — Insufficiently Protected Credentials
Disable persisted checkout credentials in PR workflows.
The
pull_requestjobs execute PR-controlled code after checkout.actions/checkoutdefaultspersist-credentialstotruein both v4 and v7, so this code can use the persistedGITHUB_TOKEN. The workflows grant onlycontents: read, which limits the token's authority. This is not a new v7 regression, but it remains an avoidable credential exposure.Set
persist-credentials: falseon these checkouts:.github/workflows/ci.yml#L21.github/workflows/ci.yml#L55.github/workflows/pr-build.yml#L21The checkouts at
.github/workflows/ci.yml#L71and.github/workflows/ci.yml#L92run only forpushevents and are not part of this PR-code path.🧰 Tools
🪛 zizmor (1.30.0)
[warning] 21-21: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
🤖 Prompt for AI Agents