skills.rest
riparino
riparinoCOMMUNITY
Explore all skills by this author →
GitHub

offensive-request-smuggling

Identify and test HTTP request smuggling vectors across front-end and back-end servers.

1|Updated Apr 27, 2026
Search Tags:#http#waf#security-testing#proxies#desync#request-smuggling
One-click install
npx skills add https://github.com/riparino/Claude-Cyber --skill offensive-request-smuggling
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: offensive-request-smuggling
Source: https://github.com/riparino/Claude-Cyber/tree/main/Claude-Red/Skills/offensive-request-smuggling
Command: npx skills add https://github.com/riparino/Claude-Cyber --skill offensive-request-smuggling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HTTP request smuggling vulnerability identification and testing across front-end proxies and back-end servers, enabling controlled assessments and remediation planning.

Core Features & Use Cases

  • CL.TE, TE.CL, TE.TE pattern testing across multi-tier architectures.
  • HTTP/2 downgrades and h2c smuggling variants for edge-case scenarios.
  • Differential timing and queue-poisoning detection to confirm desync.
  • WAF bypass considerations and defensive remediation guidance.
  • Comprehensive documentation of attack steps, risk, and mitigation strategies.

Quick Start

Ask Claude to load this skill and follow the full HTTP request smuggling methodology against your target environment.

Frequently Asked Questions about offensive-request-smuggling

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

FAQPage Schema
How do I test for HTTP request smuggling vulnerabilities across reverse proxies?▼

To test for HTTP request smuggling, apply a structured methodology to identify desync vectors between front-end and back-end servers, covering CL.TE, TE.CL, and TE.TE pattern testing across multi-tier architectures.

What is HTTP request smuggling and when do I need to test for it?▼

HTTP request smuggling is a desync vulnerability affecting front-end and back-end server communication. You need to test for it during security assessments of reverse proxies, load balancers, and HTTP/2 transitions to prevent queue poisoning.

How do I detect CL.TE and TE.CL desync patterns during security testing?▼

Detect CL.TE and TE.CL desync patterns using differential timing analysis and queue-poisoning detection to confirm HTTP request smuggling across multi-tier proxy architectures.

Can I use this methodology to bypass WAF protections during request smuggling tests?▼

Yes, the HTTP request smuggling testing methodology includes specific WAF bypass considerations and defensive remediation guidance to evaluate security controls during security assessments.

Does this request smuggling testing approach cover HTTP/2 downgrades and h2c smuggling?▼

Yes, the request smuggling testing methodology covers HTTP/2 downgrades and h2c smuggling variants to evaluate edge-case desync scenarios during security assessments.

What is the best way to document HTTP request smuggling risks and remediation?▼

The best way to document request smuggling risks is by following a structured methodology that provides comprehensive documentation of attack steps, risk factors, and mitigation strategies for remediation planning.

Related Skills

Explore More Software Engineering Skills→
dreadnodedreadnode
11

te0-request-smuggling

Detect TE.0 HTTP request smuggling in reverse proxy and backend architectures.

Official
Intermediate
inbharataiinbharatai
22

threat-modeler

Perform STRIDE analysis and generate attack trees for software systems.

Community
Advanced
jinyimeng01jinyimeng01
54

http-smuggling

Detect HTTP request smuggling vulnerabilities via CL.TE, TE.CL, and TE.TE testing.

Community
Advanced
yaklangyaklang
1.6k

request-smuggling

Identify and test HTTP request smuggling and desync vulnerabilities across proxies, CDNs, and origin servers.

Official
Advanced