> 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/access-control/bypassing-access-control-based-on-http-method.md).

# 通过 HTTP 方法绕过访问控制

通过 HTTP 方法绕过访问控制，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。

### 基于方法的访问控制可以被绕过

在本实验中，访问控制部分取决于所使用的 HTTP 方法。使用 *administrator:admin* 凭据后，管理面板即可自由查看。

目标是使用 *wiener:peter* 凭据，并利用控制实现中的错误将角色分配为管理员。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-1cc602e3bd6c89cbf2e2eed6d9a9571ca83064ae%2F%7B8AB498A1-1904-4707-905C-D860EE732248%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

以管理员身份登录后，我们发现了一个用于提升或降低用户权限的界面。/ 通过拦截修改时发送的请求：

```http
POST /admin-roles
username=carlos&action=upgrade
```

当以 **POST**.

然而，当尝试使用 wiener 会话重放此请求时，应用程序返回访问被拒绝消息。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-290547264291ea2fefbd0ed6ed6452837e4348fc%2F%7B95C407C9-E23B-4E6C-932B-7CC6C121A993%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

然而，如果将 POST 方法替换为 **GET**，控制失效：

```http
GET /admin-roles?username=wiener&action=upgrade
```

此请求通过并返回一个 **200 OK**，这使得可以将 wiener 的权限提升为管理员。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-20315ff94c06fd0abe4e025dca757ca720d7d898%2F%7B3FA4D10C-6735-4843-B5E8-83635038B93A%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/access-control/bypassing-access-control-based-on-http-method.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.
