Skip to content

fix: Prevent command injection in GitHub Actions workflow#1

Open
fix-it-felix-sentry[bot] wants to merge 1 commit intomainfrom
fix-vuln-1091-command-injection
Open

fix: Prevent command injection in GitHub Actions workflow#1
fix-it-felix-sentry[bot] wants to merge 1 commit intomainfrom
fix-vuln-1091-command-injection

Conversation

@fix-it-felix-sentry
Copy link
Copy Markdown

Summary

This PR fixes a high-severity security vulnerability (command injection) in the GitHub Actions workflow by preventing direct interpolation of user-controllable input values.

Changes

  • Move inputs.rust-version and inputs.targets to environment variables (RUST_VERSION, TARGETS)
  • Add proper quoting around all variable usages in the shell script
  • Prevent direct interpolation of potentially untrusted input using ${{ }} syntax in the run: block

Security Impact

The previous implementation directly interpolated inputs.rust-version and inputs.targets values into shell commands, which could allow an attacker to inject malicious code if these inputs were compromised. This fix follows GitHub's security best practices by using intermediate environment variables.

Related Issues

References

Move inputs.rust-version and inputs.targets to environment variables
to prevent potential command injection vulnerabilities. This follows
GitHub security best practices for handling untrusted input in workflows.

The fix:
- Moves inputs to env variables (RUST_VERSION, TARGETS)
- Quotes all variable usages in the shell script
- Prevents direct interpolation of user-controllable values

Fixes: VULN-1091
Related: EAP-400

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
@linear
Copy link
Copy Markdown

linear bot commented Feb 18, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants