competition-request-normalization-smuggling

Diagnose HTTP parser differentials and request smuggling across proxy and backend hops.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-request-normalization-smuggling-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-request-normalization-smuggling
Source: https://github.com/dbx0/skills/tree/main/skills/web-appsec/initial-access/competition-request-normalization-smuggling
Command: npx skills add https://github.com/dbx0/skills --skill competition-request-normalization-smuggling-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a request is interpreted differently by a front proxy, gateway, and backend server, attackers can reach hidden routes or bypass controls, and testers struggle to pinpoint which hop diverges. This Skill provides a structured workflow to map parsing boundaries, prove differential interpretation, and reduce the finding to a minimal replayable smuggling chain in CTF sandbox environments. ## Core Features & Use Cases - Parse Boundary Mapping: Record path decoding, slash and dot-segment handling, header canonicalization, Host derivation, and CL/TE framing behavior at every hop from edge proxy to backend. - Differential Proof: Build paired requests differing in exactly one canonicalization dimension, then capture proxy logs, backend logs, and route matches to show where interpretation diverges. - Decisive Chain Reduction: Compress findings into a minimal crafted request -> parser differential -> unintended route or hidden endpoint -> observable effect, with explicit root-cause attribution. - Use Case: During a CTF web challenge, you suspect a hidden admin endpoint is reachable only when the frontend normalizes a path differently than the backend. Use this Skill to craft baseline and differential requests, identify the exact normalization delta, and reproduce the smuggling route. ## Quick Start Ask the agent to trace how a crafted request is parsed differently across the proxy and backend hops and reproduce the minimal differential request that reaches the hidden route.

Frequently Asked Questions about competition-request-normalization-smuggling

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

FAQPage Schema
How do I detect HTTP request smuggling between a proxy and backend?

Send paired requests that differ in exactly one dimension, such as Content-Length versus Transfer-Encoding framing or path encoding, then compare proxy logs against backend route matches. Divergence in routing or body boundaries confirms a parser differential.

What is path normalization drift in web servers?

Path normalization drift occurs when different hops decode URLs, collapse slashes, handle dot segments, or apply case rules inconsistently. A request rejected by the frontend may be rewritten into a valid backend route, exposing hidden endpoints.

How do CL/TE mismatches cause request smuggling?

When the frontend prioritizes Content-Length and the backend prioritizes Transfer-Encoding, the two disagree on where one request ends and the next begins. This lets a crafted request prefix get smuggled into another user's request.

When should I use this Skill instead of a general routing analysis?

Use it when the root cause involves framing or normalization differences between parsing hops, and only after the ctf-sandbox-orchestrator has established sandbox assumptions. If the issue is purely runtime routing without framing tricks, hand off to the runtime routing skill.

What evidence should I preserve when reporting a parser differential?

Keep the raw baseline and differential request pair, each hop's parser decision and route match, and the final routed target. Also record the exact normalization or framing delta that flips behavior and one minimal replayable request.