> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/web/host-header.md). # Host Header Attacks Host header attacks, password reset poisoning, routing-based SSRF, cache poisoning, and ambiguous request handling. Host Header Attacks notes for PortSwigger Web Security Academy labs, focused on practical testing steps, Burp Suite validation, payload behavior, and exploitation workflow. ## Testing Workflow 1. Identify the vulnerable feature and the relevant request, parameter, header, cookie, or browser-side sink. 2. Reproduce the behavior in Burp Suite with a minimal payload before escalating the attack. 3. Validate impact with a clear proof of concept, such as account access, data disclosure, code execution, SSRF, or state change. 4. Keep payloads, URLs, tokens, and lab credentials unchanged while documenting the exploitation path. ## Labs
Authentication Bypass via Host Header
Basic Poisoning of the Password Reset Mechanism
Bypass of Connection State Validation
Bypassing Validation by Connection State
Password Reset Poisoning via Dangling Markup
Routing Based SSRF
SSRF via Incorrect Parsing of Request
SSRF via Incorrect Query Parsing
Web Cache Poisoning via Ambiguous Requests
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/web/host-header.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.