remove usage of dynamic GitHub actions variable #22725
Open
+7
−5
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
github-actions
bot
added
type/ci
sanikachavan5
added
pr/no-changelog
dduzgun-security
changed the title
| @@ -562,6 +562,8 @@ jobs: | |||
| # Capturing in an env var makes this safe against GHA shell injection via commit message. | |||
| # See https://securitylab.github.com/research/github-actions-untrusted-input/ | |||
| COMMIT_MESSAGE_FULL: ${{ github.event.head_commit.message }} | |||
| # Capturing workflow name in env var to prevent shell injection | |||
| WORKFLOW_NAME: ${{ github.workflow }} | |||
There was a problem hiding this comment.
Nice, having that as en env sanitizes the value.
dduzgun-security
approved these changes
Sep 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
use hardcoded names for preventing attacks
Testing & Reproduction steps
Links
PR Checklist
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.