Fix: Remove runOn: folderOpen to Prevent Code Injection via VSCode Tasks #251177
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.
vscode/.vscode/tasks.json
Line 201 in 62f57f9
vscode/.vscode/tasks.json
Line 223 in 62f57f9
Fix Arbitary code injection in
.vscode/tasks.json
configuration by removing all instances of"runOn": "folderOpen"
. This field can cause tasks to execute automatically when the workspace is opened, which may lead to unintended command execution especially if the workspace is opened in an untrusted environment.Changes:
"runOn": "folderOpen"
triggers to prevent automatic task execution.args
andcommand
fields using${workspaceFolder}
.Why this is important:
Automatic task execution via
runOn
can pose a Remote Code Execution (RCE) vector if the workspace is opened blindly or if a malicious contributor introduces unsafe scripts into the task list. This fix aligns with security best practices in developer environments and improves the safety of the project's developer experience.Case ID 🎟️:
98466
Report 📄 :
VULN-155917