Potential fix for code scanning alert no. 2: Code injection #152
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/codeharborhub/tutorial/security/code-scanning/2
To fix the problem, we should stop interpolating the untrusted
github.event.issue.bodydirectly into the shell script and instead pass it via an environment variable, then read it using native shell syntax ($ISSUE_BODY). This avoids GitHub Actions expression injection in the shell context while preserving existing behavior.Concretely, in the
Check for Security and Truststep (lines 43–49), we will:env:section that setsISSUE_BODY: ${{ github.event.issue.body }}.issue_body="$ISSUE_BODY"(or just use$ISSUE_BODYdirectly) instead ofissue_body="${{ github.event.issue.body }}".We will leave the logic of the checks unchanged. No additional imports or external tools are needed, and no other steps in the file are modified.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.