> 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/ports-and-services/http-and-https-80-443/http-https-heartbleed-vulnerability.md).

# HTTP/HTTPS - Heartbleed 漏洞

使用 ssltest.py 和过滤后的输出审查来验证 Heartbleed 漏洞。

如果 **心脏出血漏洞** 如果怀疑网站存在该漏洞，请使用以下 Python 脚本进行验证：

{% embed url="<https://github.com/vulhub/vulhub/blob/master/openssl/CVE-2014-0160/ssltest.py>" %}

```bash
python3 ssltest.py 127.0.0.1 -p 8443
```

如果出现如下内容：

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-2d607c49eba4fe4ac1a45fb91ad1350b57bb5f5b%2FPasted%20image%2020230809205346.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

过滤掉重复噪声，只保留有用输出：

```bash
python3 ssltest.py 127.0.0.1 -p 8443 | grep "01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01" -v
```

在这种情况下，不会出现有用数据。在存在漏洞的目标上，此输出可能会泄露敏感内存内容。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5b31807952d990c9d988cf3f8f842a4354ec0cc4%2FPasted%20image%2020230809205442.png?alt=media" alt="" width="563"><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/ports-and-services/http-and-https-80-443/http-https-heartbleed-vulnerability.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.