hunt-host-header

Detect Host header injection vulnerabilities including password reset poisoning, cache poisoning, and SSRF.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/inventashif/helpful-code-sidekick --skill hunt-host-header-inventashif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-host-header
Source: https://github.com/inventashif/helpful-code-sidekick/tree/main/scripts/hackerai/skills/bughunter/hunt-host-header
Command: npx skills add https://github.com/inventashif/helpful-code-sidekick --skill hunt-host-header-inventashif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications that trust the Host or X-Forwarded-Host headers can be exploited for account takeover, cache poisoning, and SSRF, but these bugs are easy to miss without a structured testing methodology. This Skill provides a phased, evidence-driven workflow for finding and validating Host header injection vulnerabilities during authorized bug bounty hunting. ## Core Features & Use Cases - Password Reset Poisoning: Tests whether forgot-password flows build reset links from attacker-controlled Host headers, enabling token capture and account takeover. - Web Cache Poisoning: Detects unkeyed X-Forwarded-Host reflection into cached responses, with false-positive checks using Vary headers, cache status, and clean-fetch verification. - SSRF and ACL Bypass: Distinguishes routing-based SSRF (Host steers the upstream to cloud metadata endpoints) from path-override attacks via X-Original-URL and X-Rewrite-URL. - Use Case: While testing a CDN-fronted target's forgot-password endpoint, inject a Burp Collaborator host via X-Forwarded-Host, confirm the reset email link points to your domain, and capture the token out-of-band as proof of account takeover. ## Quick Start Ask the AI to test the target's forgot-password endpoint for Host header injection using a Collaborator domain and validate whether the reset link uses the injected host.

Frequently Asked Questions about hunt-host-header

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

FAQPage Schema
How do I test for Host header injection in password reset flows?

Send a POST to the forgot-password endpoint with an attacker-controlled Host or X-Forwarded-Host header, then check your own test account's email. If the reset link uses the injected host, the token can be captured for account takeover.

How to confirm web cache poisoning via X-Forwarded-Host?

Verify the injected host is reflected into an absolute URL in the response, then poison a cache key and re-fetch the same URL without the header. If the clean request still returns the payload, shared-cache poisoning is proven.

What is the difference between routing-based SSRF and X-Original-URL attacks?

Routing-based SSRF uses the Host header to steer the front-end's upstream selection, such as targeting 169.254.169.254 for cloud metadata. X-Original-URL and X-Rewrite-URL override the routed path to bypass edge ACLs while the real Host stays unchanged.

Why is a reflected Host header not always a vulnerability?

Reflection alone proves nothing if the header is keyed in Vary, the response is never cached, or the mailer rewrites links to a fixed SITE_URL. You must confirm the payload reaches other users, the email body, or an internal target.

Can Host header injection lead to account takeover?

Yes, when password reset links or OAuth redirect URIs are built from the request Host. Injecting a Collaborator domain lets you capture the reset token or authorization code out-of-band, which is rated Critical severity.