exploiting-http-request-smuggling

Probe HTTP parsing discrepancies to detect CL.TE, TE.CL, and TE.TE smuggling variants.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Acczdy/MoZiSec --skill exploiting-http-request-smuggling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploiting-http-request-smuggling
Source: https://github.com/Acczdy/MoZiSec/tree/main/web-security/.claude/skills/exploiting-http-request-smuggling
Command: npx skills add https://github.com/Acczdy/MoZiSec --skill exploiting-http-request-smuggling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

HTTP request smuggling vulnerabilities enable attackers to bypass front-end security controls by desynchronizing request boundaries between a front-end proxy/CDN and the origin server. This Skill provides guidance and automated probes to detect CL.TE, TE.CL, and TE.TE smuggling variants, and demonstrates practical exploitation paths in authorized testing environments.

Core Features & Use Cases

  • Automated detection of the three major smuggling variants (CL.TE, TE.CL, TE.TE) using crafted HTTP requests.
  • Hands-on guidance for safe, authorized testing in lab or pentest engagements, including both manual and automated approaches.
  • Generates structured results and practical remediation-oriented recommendations for front-end and back-end parsing consistency.

Quick Start

Run the detection agent against a target URL to generate a comprehensive smuggling report.

Frequently Asked Questions about exploiting-http-request-smuggling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect HTTP request smuggling vulnerabilities in web applications behind proxies?

Detect HTTP request smuggling vulnerabilities by probing front-end and back-end HTTP parsing discrepancies using time-based and differential probes. This identifies CL.TE, TE.CL, and TE.TE smuggling variants through crafted HTTP requests during authorized security assessments.

What is the difference between CL.TE and TE.CL HTTP request smuggling variants?

CL.TE and TE.CL HTTP request smuggling variants differ in how front-end and back-end servers prioritize conflicting Content-Length and Transfer-Encoding headers. The detection probes exploit these specific parsing discrepancies to desynchronize request boundaries.

Can I use automated tooling for HTTP request smuggling detection during penetration testing?

You can use automated tooling and scripts for HTTP request smuggling detection during penetration testing. The probes apply time-based and differential techniques using raw sockets or automated methods to generate structured findings suitable for remediation.

Does HTTP request smuggling detection work with applications behind CDNs?

HTTP request smuggling detection works with web applications behind proxies or CDNs. It targets the desynchronization of request boundaries between the front-end proxy or CDN and the origin server by identifying parsing discrepancies.

How to generate structured findings for HTTP request smuggling remediation?

Generate structured findings for HTTP request smuggling remediation by running detection probes against target URLs. The process outputs comprehensive smuggling reports detailing CL.TE, TE.CL, and TE.TE variants and practical recommendations for front-end and back-end parsing consistency.

Why does HTTP request smuggling bypass front-end security controls?

HTTP request smuggling bypasses front-end security controls by desynchronizing request boundaries between a front-end proxy or CDN and the origin server. Attackers exploit parsing discrepancies to manipulate the interpreted request flow and bypass access restrictions.