Individual skill
header-injection
HTTP header injection — CRLF/response splitting, Host-header cache poisoning, X-Forwarded-* abuse, Content-Disposition/Set-Cookie injection, and password-reset link poisoning via unvalidated header values.
packages/decepticon/decepticon/skills/standard/exploit/web/header-injection/SKILL.md
Source commit df879550544d36b6b1e69062f05adae28537adf2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 6,563
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- cybersecurity Repository topic
- hacking Repository topic
- langchain Repository topic
- langgraph Repository topic
- llm Repository topic
- generative-ai Repository topic
- pentesting Repository topic
- pentest Repository topic
- web-application,-injection,-crlf,-cache-poisoning,-host-header Declared skill tag
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# HTTP Header Injection
Header injection turns user-controlled input into HTTP protocol control. When server code copies a request value into a response header without CR/LF stripping, an attacker can terminate the current header and inject new headers or an entire second HTTP response. At the cache layer, headers that influence the response body but are excluded from the cache key enable persistent cache poisoning. The same family of bugs drives Host-header password-reset link hijacking, `X-Forwarded-For` rate-limit bypass, and `Content-Disposition` filename injection.
**Authorized use only.** Only test systems you are explicitly authorized to assess. Cache poisoning attacks affect all users of a shared cache resource.
## Attack Surface
- Query/body/path parameters echoed into `Location`, `Set-Cookie`, `Content-Type`, `Content-Disposition`, `Link`, or custom `X-*` headers
- Request headers re-reflected into responses: `Referer`, `User-Agent`, `X-Forwarded-Host`, correlation IDs
- Password-reset / account-recovery flows where the reset link is built from the `Host` header
- OAuth/SSO redirect flows where `Location` is derived from user input
- CDN/reverse-proxy stacks where `X-Forwarded-Host` or `X-Forwarded-Proto` is echoed into canonical URLs
- `Content-Disposition: attachment; filename=<user_input>` file-download endpoints