What problem does it solve?
HTTP/2-specific request/response desynchronization and framing weaknesses are often missed by generic HTTP request-smuggling guidance, causing you to test with the wrong assumptions and miss real vulnerabilities.
Core Features & Use Cases
- h2c Upgrade Smuggling Guidance: Bypass HTTP/2-unsupported proxy enforcement by using the HTTP/1.1 Upgrade mechanism to reach a backend that speaks HTTP/2.
- Pseudo-Header Manipulation & Routing Confusion: Identify access-control and vhost routing discrepancies caused by
:path, :authority, and :scheme handling differences across proxy vs backend.
- HPACK & Multiplexing Attack Patterns: Use HTTP/2 compression-context and multiplexing behaviors to explore oracle-style leakage, race conditions, and resource exhaustion paths.
- H2→H1 Downgrade Flaw Checks: Look for header injection and smuggling-like effects that appear only when intermediaries translate HTTP/2 into HTTP/1.1.
Quick Start
Ask an authorized testing agent to apply the HTTP/2 decision tree to your target, first verifying HTTP/2 and any h2c upgrade behavior, then attempting pseudo-header discrepancies, downgrade-related header injection, and multiplexing-focused race/DoS probes while recording reproducible evidence and safe stop conditions.