> 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/business-logic.md).

# 业务逻辑

业务逻辑缺陷、工作流绕过、对客户端信任的滥用、不一致的控制以及应用程序逻辑利用。

PortSwigger Web Security Academy 实验室的业务逻辑笔记，重点关注实际测试步骤、Burp Suite 验证、载荷行为以及利用流程。

## 测试流程

1. 识别存在漏洞的功能，以及相关的请求、参数、请求头、Cookie 或浏览器端 sink。
2. 在进一步发起攻击之前，先在 Burp Suite 中使用最小有效载荷复现该行为。
3. 使用清晰的概念验证来验证影响，例如账户访问、数据泄露、代码执行、SSRF 或状态变更。
4. 在记录利用路径时，保持有效载荷、URL、令牌和实验室凭据不变。

## 实验

<table><thead><tr><th data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/zh/web/business-logic/authentication-bypass-via-encryption-oracle.md">通过加密预言机绕过身份验证</a></td></tr><tr><td><a href="/zh/web/business-logic/bypassing-flawed-state-machine.md">通过有缺陷的状态机绕过</a></td></tr><tr><td><a href="/zh/web/business-logic/bypassing-access-controls-by-inconsistent-parsing-of-email-addresses.md">通过对电子邮件地址的不一致解析绕过访问控制</a></td></tr><tr><td><a href="/zh/web/business-logic/bypassing-authentication-via-encryption-oracle.md">通过加密预言机绕过身份验证</a></td></tr><tr><td><a href="/zh/web/business-logic/excessive-trust-in-client-side-controls.md">对客户端控制过度信任</a></td></tr><tr><td><a href="/zh/web/business-logic/failed-state-machine-workaround.md">有缺陷的状态机变通方法</a></td></tr><tr><td><a href="/zh/web/business-logic/high-level-logic-vulnerability.md">高级逻辑漏洞</a></td></tr><tr><td><a href="/zh/web/business-logic/inconsistent-handling-of-exceptional-input.md">对异常输入的不一致处理</a></td></tr><tr><td><a href="/zh/web/business-logic/inconsistent-management-of-exceptional-entries.md">对异常条目的不一致管理</a></td></tr><tr><td><a href="/zh/web/business-logic/inconsistent-security-controls.md">不一致的安全控制</a></td></tr><tr><td><a href="/zh/web/business-logic/insufficient-workflow-validation.md">工作流验证不足</a></td></tr><tr><td><a href="/zh/web/business-logic/logical-flaw-allowing-you-to-generate-infinite-money.md">允许你生成无限金钱的逻辑缺陷</a></td></tr><tr><td><a href="/zh/web/business-logic/low-isolation-on-a-dual-use-endpoint.md">双用途端点上的低隔离</a></td></tr><tr><td><a href="/zh/web/business-logic/low-level-logic-flaw.md">底层逻辑失败</a></td></tr><tr><td><a href="/zh/web/business-logic/overconfidence-on-the-client-side.md">对客户端侧过度自信</a></td></tr><tr><td><a href="/zh/web/business-logic/flawed-business-rules.md">应用不当的业务规则</a></td></tr><tr><td><a href="/zh/web/business-logic/weak-isolation-on-dual-use-endpoint.md">双用途端点上的弱隔离</a></td></tr></tbody></table>


---

# 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/business-logic.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.
