hunt-http-smuggling

Detect and validate HTTP request smuggling vectors between proxies and servers.

13|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/pdparchitect/rook --skill hunt-http-smuggling-pdparchitect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-http-smuggling
Source: https://github.com/pdparchitect/rook/tree/main/skills/hunt-http-smuggling
Command: npx skills add https://github.com/pdparchitect/rook --skill hunt-http-smuggling-pdparchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the critical security risk where front-end proxies and back-end servers disagree on request boundaries, allowing attackers to smuggle requests, poison caches, or bypass authentication.

Core Features & Use Cases

  • Protocol Confusion Detection: Identifies CL.TE, TE.CL, and modern H2.CL/H2.TE smuggling vectors.
  • Impact Validation: Provides methodologies for confirming cache poisoning, credential theft, and authorization bypass chains.
  • Use Case: Use this skill when auditing CDN-fronted architectures or load balancers to determine if they are susceptible to request desynchronization attacks.

Quick Start

Use the hunt-http-smuggling skill to probe the target domain for HTTP request smuggling vulnerabilities using the recommended timing-delay technique.

Frequently Asked Questions about hunt-http-smuggling

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

FAQPage Schema
What is HTTP request smuggling and how do proxy-server parsing inconsistencies cause it?

HTTP request smuggling occurs when front-end proxies and back-end servers disagree on request boundaries, allowing attackers to smuggle malicious requests, poison caches, or bypass authentication mechanisms.

How do I detect CL.TE and TE.CL request smuggling vulnerabilities in a web application?

You detect CL.TE and TE.CL smuggling by injecting protocol-specific payloads and performing precise timing analysis to confirm exploitable desynchronization between the front-end proxy and back-end server.

Can I test for HTTP request smuggling on CDN-fronted architectures and load balancers?

Yes, you can audit CDN-fronted architectures and load balancer stacks to determine if they are susceptible to request desynchronization attacks caused by parsing inconsistencies.

How do I validate the impact of an HTTP request smuggling vulnerability?

You validate the impact by applying methodologies that confirm cache poisoning, credential theft, and authorization bypass chains resulting from the detected request desynchronization.

Does this HTTP smuggling detection technique support H2 downgrade attack vectors?

Yes, the detection technique identifies modern H2.CL and H2.TE smuggling vectors, covering HTTP/2 downgrade attacks in addition to traditional CL.TE and TE.CL vectors.

What is the best way to probe a target domain for HTTP request smuggling flaws?

The recommended approach is probing the target domain using the timing-delay technique, which requires precise timing analysis to detect desynchronization between proxy and server boundaries.