http-request-smuggling

Detect and exploit HTTP request smuggling via conflicting Content-Length and Transfer-Encoding headers.

6|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/securityfortech/hacking-skills --skill http-request-smuggling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: http-request-smuggling
Source: https://github.com/securityfortech/hacking-skills/tree/main/skills/web/injection/http-request-smuggling
Command: npx skills add https://github.com/securityfortech/hacking-skills --skill http-request-smuggling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and exploit vulnerabilities in how web servers and proxies interpret HTTP requests, leading to unauthorized access and data breaches.

Core Features & Use Cases

  • Vulnerability Detection: Identifies HTTP Request Smuggling flaws using CL.TE, TE.CL, and TE.TE techniques.
  • Exploitation: Bypasses access controls, poisons caches, hijacks sessions, and captures user requests.
  • Use Case: An attacker can use this skill to smuggle a request to an admin-only endpoint that is normally protected by a front-end proxy, gaining unauthorized access.

Quick Start

Use the http-request-smuggling skill to detect CL.TE vulnerabilities against the target URL.

Frequently Asked Questions about http-request-smuggling

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

FAQPage Schema
How does HTTP request smuggling bypass front-end proxy access controls?

HTTP request smuggling bypasses front-end proxy access controls by exploiting conflicting Content-Length and Transfer-Encoding headers, causing the back-end server to process a smuggled malicious request independently of front-end restrictions.

How do I detect CL.TE and TE.CL HTTP request smuggling vulnerabilities?

You can detect CL.TE and TE.CL vulnerabilities using Burp Suite with the HTTP Request Smuggler extension, which automates probing for conflicting header interpretations between front-end proxies and back-end servers.

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

CL.TE and TE.CL techniques exploit server disagreements on header priority: CL.TE processes Content-Length first then Transfer-Encoding, while TE.CL prioritizes Transfer-Encoding then Content-Length, enabling request boundary manipulation.

Can I hijack user sessions or poison caches using HTTP desync vulnerabilities?

Yes, you can exploit HTTP desync vulnerabilities to hijack sessions or poison caches by smuggling malicious requests that capture subsequent user traffic or inject unauthorized content into shared cache entries.

Do I need Burp Suite to automate HTTP request smuggling detection?

Yes, this approach requires Burp Suite with the HTTP Request Smuggler extension to effectively automate the detection and exploitation of CL.TE, TE.CL, and TE.TE request smuggling vulnerabilities.