Competition Request Normalization Smuggling
Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.
Use this skill when request interpretation changes between proxy, middleware, and backend parser layers.
Reply in Simplified Chinese unless the user explicitly requests English.
Quick Start
- Map every parsing hop: client-facing proxy, gateway, app server, and downstream service.
- Record path normalization, header canonicalization, transfer framing, and host derivation at each hop.
- Capture one accepted baseline request and one differential request with minimal delta.
- Prove which hop interprets the request differently.
- Reproduce one minimal differential path that yields decisive behavior.
Workflow
1. Map Parse And Routing Boundaries
- Record
Host, forwarded headers, path decoding, slash collapsing, dot-segment handling, and case behavior.
- Note
Content-Length, Transfer-Encoding, chunk framing, and connection reuse behavior when relevant.
- Keep edge parser and backend parser decisions side by side.
2. Prove Differential Interpretation
- Build paired requests that differ in one canonicalization dimension only.
- Capture proxy logs, backend logs, route match, and downstream request shape.
- Show where route, auth scope, or body boundary diverges.
3. Reduce To Decisive Smuggling Chain
- Compress to: crafted request -> parser differential across hops -> unintended routed request or hidden endpoint reach -> resulting effect.
- State whether root cause is path normalization drift, header ambiguity, transfer framing differential, or host-derivation confusion.
- If the chain becomes primarily runtime routing without framing tricks, hand off to runtime routing skill.
Read This Reference
- Load
references/request-normalization-smuggling.md for parse-differential checklist and evidence packaging.
What To Preserve
- Raw request pairs, hop-by-hop interpretation, and final routed target
- Exact normalization or framing delta that flips behavior
- One minimal replayable differential request path
1---2name: competition-request-normalization-smuggling3description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for parser differentials, HTTP normalization gaps, ambiguous headers, path decoding drift, transfer-framing mismatches, and request smuggling routes. Use when the user asks to trace proxy and backend parse differences, conflicting path normalization, Host or forwarded-header ambiguity, CL/TE issues, or routing outcomes that differ across hops. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.4---5
6# Competition Request Normalization Smuggling
7
8Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.
9
10Use this skill when request interpretation changes between proxy, middleware, and backend parser layers.
11
12Reply in Simplified Chinese unless the user explicitly requests English.
13
14## Quick Start
15
161. Map every parsing hop: client-facing proxy, gateway, app server, and downstream service.
172. Record path normalization, header canonicalization, transfer framing, and host derivation at each hop.
183. Capture one accepted baseline request and one differential request with minimal delta.
194. Prove which hop interprets the request differently.
205. Reproduce one minimal differential path that yields decisive behavior.
21
22## Workflow
23
24### 1. Map Parse And Routing Boundaries
25
26- Record `Host`, forwarded headers, path decoding, slash collapsing, dot-segment handling, and case behavior.
27- Note `Content-Length`, `Transfer-Encoding`, chunk framing, and connection reuse behavior when relevant.
28- Keep edge parser and backend parser decisions side by side.
29
30### 2. Prove Differential Interpretation
31
32- Build paired requests that differ in one canonicalization dimension only.
33- Capture proxy logs, backend logs, route match, and downstream request shape.
34- Show where route, auth scope, or body boundary diverges.
35
36### 3. Reduce To Decisive Smuggling Chain
37
38- Compress to: crafted request -> parser differential across hops -> unintended routed request or hidden endpoint reach -> resulting effect.
39- State whether root cause is path normalization drift, header ambiguity, transfer framing differential, or host-derivation confusion.
40- If the chain becomes primarily runtime routing without framing tricks, hand off to runtime routing skill.
41
42## Read This Reference
43
44- Load `references/request-normalization-smuggling.md` for parse-differential checklist and evidence packaging.
45
46## What To Preserve
47
48- Raw request pairs, hop-by-hop interpretation, and final routed target
49- Exact normalization or framing delta that flips behavior
50- One minimal replayable differential request path
gabrielmoreira