Ffix for code scanning alert no. 28: Workflow does not contain permissions #3449
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/AFLplusplus/LibAFL/security/code-scanning/28
To fix the issue, you should add a
permissions
block to the workflow to explicitly restrict the default permissions granted to GITHUB_TOKEN. This is best applied at the workflow root level (abovejobs:
or immediately under the workflow name / triggers) to enforce least privilege for all jobs, unless specific jobs require greater permissions and override it. In this case, settingpermissions: contents: read
is safest and matches the recommended minimal base. You only need to edit the.github/workflows/build_and_test.yml
file, adding the following block directly after thename: build and test
line and before theon:
block (i.e., as the first keys in the YAML after the name).No additional imports, methods, or definitions are needed for YAML workflows—just a one-line addition.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.