# Command Injection (CWE-78)

User input is passed unsanitized to system shell commands, allowing attackers to execute arbitrary commands on the server.

**Stack:** Go

- Prevalence: Common Found in many applications
- Impact: Critical Full server compromise
- Prevention: Avoid shell Use execFile, not exec

**OWASP:** Injection (A03:2021-Injection) - #3

## Description

This could allow attackers to execute unexpected, dangerous commands directly on the operating system. This weakness can lead to a vulnerability in environments in which the attacker does not have direct access to the operating system.

## Prevention

1 Shoulder डिटेक्शन नियमों पर आधारित OS Command Injection के लिए रोकथाम रणनीतियाँ।

### Go

Use exec.Command with explicit arguments, never shell invocation

## Warning Signs

- [CRITICAL] user input flowing to os/exec command execution, enabling OS command injection

## Consequences

- अनधिकृत कमांड निष्पादित करना
- एप्लिकेशन डेटा पढ़ना
- सुरक्षा तंत्र को बायपास करना

## Mitigations

- बाहरी प्रक्रियाओं के बजाय लाइब्रेरी कॉल का उपयोग करें
- यदि Runtime.exec() का उपयोग कर रहे हैं, तो उस संस्करण का उपयोग करें जो आर्ग्युमेंट्स का ऐरे लेता है
- ऐसे संरचित तंत्रों का उपयोग करें जो डेटा और कोड के बीच पृथक्करण स्वतः लागू करते हैं

## Detection

- Total rules: 3
- Critical: 3
- Languages: go, javascript, typescript, python

## Rules by Language

### Go (1 rules)

- **Command Injection via os/exec** [CRITICAL]: Detects user input flowing to os/exec command execution, enabling OS command injection.
  - Remediation: Use exec.Command with explicit arguments and validate input against an allowlist.

```go
allowed := map[string]bool{"file1.txt": true, "file2.txt": true}
if !allowed[userInput] {
    return errors.New("not allowed")
}
cmd := exec.Command("cat", userInput)
```

Learn more: https://shoulder.dev/learn/go/cwe-78/command-injection