Security vulnerabilities and automated fixes for execsync issues
3 posts found
A critical command injection vulnerability in `scripts/check-links.js` was fixed by replacing `execSync()` with `execFileSync()`, eliminating shell interpretation of user-controlled repository names. This proactive hardening prevents potential remote code execution in the GitHub CLI integration workflow.
A high-severity command injection vulnerability in `gateway-workflow-dispatcher-v2.js` allowed arbitrary command execution through unsanitized input passed to `execSync`. The fix replaces `execSync` with `execFileSync`, eliminating shell interpretation and preventing attackers from injecting malicious commands through the `eventText` parameter.
A critical command injection vulnerability was discovered in `packages/core/bin/cli.js` where the `copyToClipboard` function used `execSync()` with shell command strings. Combined with insufficient filename sanitization in the cache functions, an attacker could inject arbitrary shell commands through malicious repository data containing shell metacharacters. The fix replaces `execSync()` with `execFileSync()` and tightens input sanitization on cache file paths.