Potential fix for code scanning alert no. 14: Workflow does not contain permissions #26
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
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
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.
Potential fix for https://github.com/pingidentity/terraform-pingone-utils/security/code-scanning/14
The best way to fix this issue is to explicitly declare the required minimal permissions for the workflow at the top level, just below the
name:field and aboveon:in.github/workflows/release-example-action.yml. At a minimum, this means adding apermissions:block that only grants what the workflow steps need. Because the workflow usessoftprops/action-gh-release@v2to publish files to a release, it does require write access to repository contents. Therefore, the appropriate permissions to specify are:This ensures that only the
contents: writescope is granted (allowing the workflow to create or modify release assets), and all other permissions are denied by default, in line with the principle of least privilege. No code logic or step behavior will change, just the workflow header will be updated.Suggested fixes powered by Copilot Autofix. Review carefully before merging.