> 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/zh/web/host-header/authentication-bypass-via-host-header.md).

# 通过 Host 头绕过身份验证

通过 Host 头绕过身份验证，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。

### Host 头认证绕过

**实验描述**

这个实验基于一个错误的服务端假设：用户权限级别是根据 HTTP 头的值来确定的 **主机**. / 通过处理这个头，可以访问仅供管理员使用的功能。

\*\* 目标：\*\*/ 进入管理面板并删除用户 **carlos**.

\*\* 观察到的初始行为\*\*

当尝试使用标准请求访问管理页面时，会被拒绝访问。

典型请求：

```http
GET /admin HTTP/2
Host: 0aa100b30336117186f29ede001a0029.web-security-academy.net
```

响应：未授权访问

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-f9c9c4f4b26bdd61bd2d0f367553a2c331369a12%2F%7B4B62D5F6-47B4-43E0-BF43-128A8E37AB47%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**漏洞分析**

当请求来自被视为“内部”或可信的主机时，应用似乎会授予高权限，例如 **localhost**. / 不会执行额外验证来确认请求的实际来源。

```http
Host: 0aa100b30336117186f29ede001a0029.web-security-academy.net
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8e1f18327882169c267bbc9c8a5ebe2ed5f546c8%2F%7BD870FDF8-AE94-45F6-AF36-3914D2F04AB3%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**利用**

只需手动更改 **主机** HTTP 请求中的头值。

修改后的请求：

```http
Host: localhost
```

结果：已获授权访问管理面板

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-6edf77cd803d2947cb21270144fcf8f5a279e569%2F%7BD9A1CBB4-5DE0-4245-B55A-E1D004716379%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**最终操作**

一旦获得管理员访问权限，就可以删除目标用户：

```bash
/admin/delete?username=carlos
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-a61f1349fc303bf9ea5189f33854ceb0191b7436%2F%7B213232A9-74E3-4DCB-A156-C15A888B25F2%7D.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/zh/web/host-header/authentication-bypass-via-host-header.md?ask=<question>&goal=<user_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.
