> 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/cors/cors-basic-origin-reflection.md).
# CORS 对来源的基础反射
CORS 对来源的基础反射笔记，适用于 PortSwigger Web Security Academy 实验室，包括利用流程、载荷测试、Burp Suite 验证和修复上下文。
### 具有基本 Origin 反射的 CORS 漏洞
利用过于宽松的 CORS 配置（服务器信任任何来源）通过带有凭据的跨域查询从管理员处获取 API 密钥 `凭据` 并将响应发送到我们的利用服务器。当 API 管理员密钥被提交到利用服务器时，练习即告完成。
* 用于连接的凭据： `wiener:peter`.
* 页面端代码从以下路径恢复 API 密钥： `/accountDetails` 并显示：
```javascript
```
这些响应头表明 `Access-Control-Allow-Credentials: true` （服务器接受带有 cookie/凭据的请求）。
* 通过测试带有 `Origin: jord4n.pro` 请求头的查询，得到返回结果（接受了反射的来源）。
```javascript
Origin: jord4n.pro
```
* 服务器会反射/允许发送的来源，因此攻击者控制的页面可以执行一个 `XMLHttpRequest` 或 `fetch` 更改为 `/accountDetails` 通过包含受害者的 cookie（`withCredentials = true`）并恢复包含 API 密钥的 JSON 响应。
```javascript
```
一旦读取到响应，就可以将其发送到服务器（例如通过 base64 编码）以供收集。
```javascript
```
{% code overflow="wrap" %}
```
10.0.3.6 2025-10-29 20:19:37 +0000 "GET /?apiKey=ewogICJ1c2VybmFtZSI6ICJhZG1pbmlzdHJhdG9yIiwKICAiZW1haWwiOiAiIiwKICAiYXBpa2V5IjogIjg2cWk4Mnh2TUdDOUdyV2dYY1RPdUN4bnVCQU9Gd3VEIiwKICAic2Vzc2lvbnMiOiBbCiAgICAiS240MzN2QVpqWU1WUTZTUE1JTmx4YzY5aHFjNVg1M24iCiAgXQp9 HTTP/1.1" 200 "user-agent: Mozilla/5.0 (Victim) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
```
{% endcode %}
操作服务器收到了一个包含编码后响应的 GET 查询，例如：
---
# 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/cors/cors-basic-origin-reflection.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.
