Exploiting HTTP Request Smuggling

Exploiting Http Request Smuggling

Overview

Cybersecurity skill for exploiting http request smuggling. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "exploiting http request smuggling"

• "Detecting and exploiting HTTP request smuggling vulnerabilities caused by Conten"

• During authorized penetration tests when the application sits behind a reverse proxy, load balancer, or CDN

• When testing infrastructure with multiple HTTP processors in the request chain (nginx + Apache, HAProxy + Gunicorn)

• For assessing applications for HTTP desynchronization vulnerabilities

• When other attack vectors are limited and you need to bypass front-end security controls

• During security assessments of multi-tier web architectures

When NOT to Use

• When you lack proper authorization for testing
• For production systems without change management
• When the task requires legal or compliance expertise beyond technical scope

Prerequisites

• Authorization: Written penetration testing agreement explicitly covering request smuggling (high-risk test)
• Burp Suite Professional: With HTTP Request Smuggler extension (Turbo Intruder)
• smuggler.py: Automated HTTP request smuggling detection tool
• curl: Compiled with HTTP/1.1 support and manual chunked encoding
• Target architecture knowledge: Understanding of proxy/server chain (front-end and back-end)
• Caution: Request smuggling can affect other users' requests; test carefully

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}

1. Reconnaissance — Gather information about the target related to http request smuggling. Identify attack surface.
2. Vulnerability Identification — Enumerate potential http request smuggling weaknesses using automated and manual techniques.
3. Exploit Development/Selection — Choose or develop exploits targeting identified http request smuggling vulnerabilities.
4. Execution — Execute the http request smuggling test in a controlled manner with proper authorization.
5. Post-Exploitation — Document the impact and extent of successful exploitation.
6. Reporting — Write detailed findings with reproduction steps, impact assessment, and remediation guidance.

Tools

• Vulnerability Scanner — Automated weakness identification
• Exploitation Framework — Controlled exploitation testing
• Reporting Tool — Findings documentation and tracking

Process

1. Reconnaissance — Gather target information, identify attack surface, enumerate services
2. Analysis/Exploitation — Execute the technique, analyze results, document findings
3. Reporting — Document IOCs, write findings, provide remediation recommendations

Verification

• All http request smuggling procedures executed completely and documented
• Findings validated against multiple data sources
• False positives identified and filtered
• Results documented with evidence and timestamps
• Recommendations provided with risk-based prioritization

Anti-Rationalization Table