competition-request-normalization-smuggling

Name: competition-request-normalization-smuggling
Author: zhaoxuya520

8.8kstars1.4kforks

How to install competition-request-normalization-smuggling?

zhaoxuya520/reverse-skill/competition-request-normalization-smuggling

$npx -y skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling

Installs into the current project.

Summary

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 par

Files · 1

View on GitHub

SKILL.md

1	# Competition Request Normalization Smuggling
2
3	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.
4
5	Use this skill when request interpretation changes between proxy, middleware, and backend parser layers.
6
7	Reply in Simplified Chinese unless the user explicitly requests English.
8
9	## Quick Start
10
11	1. Map every parsing hop: client-facing proxy, gateway, app server, and downstream service.
12	2. Record path normalization, header canonicalization, transfer framing, and host derivation at each hop.
13	3. Capture one accepted baseline request and one differential request with minimal delta.
14	4. Prove which hop interprets the request differently.
15	5. Reproduce one minimal differential path that yields decisive behavior.
16
17	## Workflow
18
19	### 1. Map Parse And Routing Boundaries
20
21	- Record `Host`, forwarded headers, path decoding, slash collapsing, dot-segment handling, and case behavior.
22	- Note `Content-Length`, `Transfer-Encoding`, chunk framing, and connection reuse behavior when relevant.
23	- Keep edge parser and backend parser decisions side by side.
24
25	### 2. Prove Differential Interpretation
26
27	- Build paired requests that differ in one canonicalization dimension only.
28	- Capture proxy logs, backend logs, route match, and downstream request shape.
29	- Show where route, auth scope, or body boundary diverges.
30
31	### 3. Reduce To Decisive Smuggling Chain
32
33	- Compress to: crafted request -> parser differential across hops -> unintended routed request or hidden endpoint reach -> resulting effect.
34	- State whether root cause is path normalization drift, header ambiguity, transfer framing differential, or host-derivation confusion.
35	- If the chain becomes primarily runtime routing without framing tricks, hand off to runtime routing skill.
36
37	## Read This Reference
38
39	- Load `references/request-normalization-smuggling.md` for parse-differential checklist and evidence packaging.
40
41	## What To Preserve
42
43	- Raw request pairs, hop-by-hop interpretation, and final routed target
44	- Exact normalization or framing delta that flips behavior
45	- One minimal replayable differential request path

People who liked this also viewed

6 picks

Type

competition-request-normalization-smuggling

8.8kstars1.4kforks

View on GitHub

How to install competition-request-normalization-smuggling?

zhaoxuya520/reverse-skill/competition-request-normalization-smuggling

$npx -y skills add zhaoxuya520/reverse-skill --skill competition-request-normalization-smuggling

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Competition Request Normalization Smuggling
2
3	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.
4
5	Use this skill when request interpretation changes between proxy, middleware, and backend parser layers.
6
7	Reply in Simplified Chinese unless the user explicitly requests English.
8
9	## Quick Start
10
11	1. Map every parsing hop: client-facing proxy, gateway, app server, and downstream service.
12	2. Record path normalization, header canonicalization, transfer framing, and host derivation at each hop.
13	3. Capture one accepted baseline request and one differential request with minimal delta.
14	4. Prove which hop interprets the request differently.
15	5. Reproduce one minimal differential path that yields decisive behavior.
16
17	## Workflow
18
19	### 1. Map Parse And Routing Boundaries
20
21	- Record `Host`, forwarded headers, path decoding, slash collapsing, dot-segment handling, and case behavior.
22	- Note `Content-Length`, `Transfer-Encoding`, chunk framing, and connection reuse behavior when relevant.
23	- Keep edge parser and backend parser decisions side by side.
24
25	### 2. Prove Differential Interpretation
26
27	- Build paired requests that differ in one canonicalization dimension only.
28	- Capture proxy logs, backend logs, route match, and downstream request shape.
29	- Show where route, auth scope, or body boundary diverges.
30
31	### 3. Reduce To Decisive Smuggling Chain
32
33	- Compress to: crafted request -> parser differential across hops -> unintended routed request or hidden endpoint reach -> resulting effect.
34	- State whether root cause is path normalization drift, header ambiguity, transfer framing differential, or host-derivation confusion.
35	- If the chain becomes primarily runtime routing without framing tricks, hand off to runtime routing skill.
36
37	## Read This Reference
38
39	- Load `references/request-normalization-smuggling.md` for parse-differential checklist and evidence packaging.
40
41	## What To Preserve
42
43	- Raw request pairs, hop-by-hop interpretation, and final routed target
44	- Exact normalization or framing delta that flips behavior
45	- One minimal replayable differential request path

People who liked this also viewed

6 picks

Type