Skip to content
cccskills
FreePublished on GitHub

competition-request-normalization-smuggling

Compare how proxies and backend servers interpret HTTP requests in a CTF sandbox. Use paired requests and logs to pinpoint differences in paths, headers, or message boundaries, then document a minimal reproduction of unintended routing.

OriginalShow the original description

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.

See how to install

Good for

  • Compare HTTP interpretation across proxies and backend servers
  • Investigate path normalization and decoding differences
  • Trace routing changes caused by ambiguous headers
  • Reproduce request smuggling caused by body boundary differences

Files included (3)

  • SKILL.md2.8 KB
  • agents/openai.yaml400 B
  • references/request-normalization-smuggling.md958 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

  1. Map every parsing hop: client-facing proxy, gateway, app server, and downstream service.
  2. Record path normalization, header canonicalization, transfer framing, and host derivation at each hop.
  3. Capture one accepted baseline request and one differential request with minimal delta.
  4. Prove which hop interprets the request differently.
  5. 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

api-security

FreeSummary

Assess authorized APIs through a ten-stage workflow covering endpoint discovery, authentication, access permissions, input handling, and request limits. Collect reproducible evidence and turn findings into regression checks that can run in a development pipeline.

  • Review API authentication and access permissions
  • Assess GraphQL and WebSocket security
  • Check request limits and unintended data exposure
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

apk-reverse

FreeSummary

Inspect Android APKs from the command line to understand app logic, permissions, and components. Supports Java decompilation, low-level code edits, rebuilding and signing, plus Frida observation of running methods and routing to native code analysis.

  • Inspecting APK entry points, components, and permissions
  • Locating login, signing, and certificate checks
  • Editing smali code and rebuilding an APK
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

attack-chain

FreeSummary

Plan and coordinate authorized penetration tests across multiple stages, from reconnaissance to access, privilege escalation, movement between systems, and impact assessment. Assign specialist skills, revise blocked paths, and maintain evidence and progress records for the final report.

  • Plan a penetration test across multiple stages
  • Assess how far a vulnerability could lead
  • Replan from existing credentials or system access
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

binary-diff

FreeSummary

Transfer known function and variable names from an older binary to a newer version. Compare disassembly and pseudocode with an LLM, produce structured mappings, and apply names and comments in IDA.

  • Migrate known function names after a software update
  • Locate kernel functions when the new PDB is unavailable
  • Find updated function addresses and structure offsets
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

Inspect compiled programs in Binary Ninja using strings, function references, and intermediate representations—views of program logic at different levels. Trace data flow and report findings with addresses, supporting evidence, confidence, and reproduction steps.

  • Tracing function calls and data flow in Binary Ninja
  • Cross-checking findings from other disassemblers
  • Automating binary analysis with the Python API
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

Automate website navigation, form filling, content collection, and Windows desktop interactions. The skill selects browser or desktop tools for the task and guides screenshot capture and desktop network traffic observation when needed.

  • Automating website login and form entry
  • Collecting page content and screenshots
  • Operating Windows desktop applications
zhaoxuya520/reverse-skill42.6KUpdated Sep 22, 2026

See all skills by zhaoxuya520

Report a problem with this skill