Potential fix for code scanning alert no. 6: Code injection #81
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/Couchbase-Ecosystem/mcp-server-couchbase/security/code-scanning/6
To fix the code injection risk, values that may be influenced by untrusted input (such as version strings from files committed to the repo) must not be interpolated into
run:blocks using${{ ... }}syntax. Instead, these should be set as environment variables at the step level and referenced using native shell variable syntax ($VAR). Specifically: in the "Notify completion" step (lines 142-148), move the assignment ofsteps.version.outputs.versionto an environment variable, then reference it within therunblock using$VERSION. The rest of the use of$VERSIONremains unchanged. This avoids shell injection, as the shell variable is properly quoted and parsed.Changes involved:
env:section to assignVERSION: ${{ steps.version.outputs.version }}.${{ steps.version.outputs.version }}with$VERSION.No changes are needed elsewhere in the file to accomplish this error fix.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.