Merged
Conversation
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension. |
![wiz-swan[bot]](https://avatars.githubusercontent.com/u/47886602?s=60&v=4){kind=small}
| permissions: | ||
| id-token: write # Required for OIDC (used for npm publish with Trusted publishing) | ||
| packages: write | ||
| contents: write |
There was a problem hiding this comment.
Workflow should not have write permissions to sensitive scopes
on resource jobs.build.permissions.contents
More Details
This rule checks that GitHub workflow does not use unnecessarily elevated token permissions. This rule fails when a workflow grants write permissions to sensitive scopes like `contents`, `pull-requests`, `packages`, or other privileged operations. Excessive token permissions increase the potential impact of a workflow compromise, allowing attackers to modify repository contents, merge pull requests, or perform other damaging actions. To prevent this risk, always apply the principle of least privilege by restricting token permissions to only what's absolutely necessary for each workflow.
Expected
Job 'build' should not have write permission for 'contents'
Found
Job 'build' has write permission for sensitive scope 'contents'
Security Frameworks: wf-id-1, wf-id-175
Rule ID: 88a7f807-7b08-451e-a9b2-7cd83e3a21a3
| runs-on: ubuntu-latest | ||
|
|
||
| permissions: | ||
| id-token: write # Required for OIDC (used for npm publish with Trusted publishing) |
There was a problem hiding this comment.
Workflow should not have write permissions to sensitive scopes
on resource jobs.build.permissions.id-token
More Details
This rule checks that GitHub workflow does not use unnecessarily elevated token permissions. This rule fails when a workflow grants write permissions to sensitive scopes like `contents`, `pull-requests`, `packages`, or other privileged operations. Excessive token permissions increase the potential impact of a workflow compromise, allowing attackers to modify repository contents, merge pull requests, or perform other damaging actions. To prevent this risk, always apply the principle of least privilege by restricting token permissions to only what's absolutely necessary for each workflow.
Expected
Job 'build' should not have write permission for 'id-token'
Found
Job 'build' has write permission for sensitive scope 'id-token'
Security Frameworks: wf-id-1, wf-id-175
Rule ID: 88a7f807-7b08-451e-a9b2-7cd83e3a21a3
|
|
||
| permissions: | ||
| id-token: write # Required for OIDC (used for npm publish with Trusted publishing) | ||
| packages: write |
There was a problem hiding this comment.
Workflow should not have write permissions to sensitive scopes
on resource jobs.build.permissions.packages
More Details
This rule checks that GitHub workflow does not use unnecessarily elevated token permissions. This rule fails when a workflow grants write permissions to sensitive scopes like `contents`, `pull-requests`, `packages`, or other privileged operations. Excessive token permissions increase the potential impact of a workflow compromise, allowing attackers to modify repository contents, merge pull requests, or perform other damaging actions. To prevent this risk, always apply the principle of least privilege by restricting token permissions to only what's absolutely necessary for each workflow.
Expected
Job 'build' should not have write permission for 'packages'
Found
Job 'build' has write permission for sensitive scope 'packages'
Security Frameworks: wf-id-1, wf-id-175
Rule ID: 88a7f807-7b08-451e-a9b2-7cd83e3a21a3
| # This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node | ||
| # For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions | ||
|
|
||
| name: Release |
There was a problem hiding this comment.
Workflow should have permissions limitations
on resource name
More Details
This rule checks that GitHub workflow has an empty permissions block to enforce least privilege. This rule fails when the workflow doesn't have a permissions block or has a non-empty permissions block with `write-all` scope, which can grant excessive permissions to workflow actions. Excessive permissions in GitHub workflows increase the risk surface in case of a compromise, potentially allowing attackers to access sensitive resources or perform unauthorized actions. To prevent this risk, always implement least privilege by explicitly defining an empty permissions block for all workflows.
Expected
GitHub workflow should have empty permissions block
Found
GitHub workflow doesn't have a permissions block defined
Security Frameworks: wf-id-175, wf-id-1
Rule ID: f140b9ff-063f-4312-ad25-dca7d00fb913
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.
No description provided.