Fix shell injection vulnerability in ShortcutsCommandRunner #691
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.
The
ShortcutsCommandRunnerwas vulnerable to shell command injection through unescapedshortcutIdentifiervalues in shell scripts. A malicious identifier likeShortcut"; rm -rf ~; echo "x"would execute arbitrary commands.Changes
Replace shell script execution with direct Process invocation in
ShortcutsCommandRunner.run()shortcutIdentifieras a separate argument array instead of interpolating into a shell stringScriptCommandRunnerApply same fix to
CommandRunner.reveal()for theshortcuts viewcommandBefore
After
This prevents shell interpretation of special characters in user-controlled input from configuration files.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.