> 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/hacking-wifi/wpa-wpa2-psk-network-attacks/wps/wps-attacks.md).

# WPS 安全评估

评估 WPS 暴露面并记录所需修复。

Wi‑Fi Protected Setup（WPS）可简化某些接入点上的客户端接入配置。

其 PIN 方法使用一个八位数字值。薄弱的实现可能会增加网络风险。

### 定义评估范围

记录每个接入点、其 BSSID、信道和固件版本。

记录评估日期和时间窗口。

### 验证 WPS 配置

使用路由器管理界面或经批准的扫描器。

记录 WPS 是否已启用，以及可用的接入方式。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FVoIrsUOur6O89a5zGzaH%2Fimage.png?alt=media&amp;token=081288a7-c621-421a-833e-4cc51adcdd18" alt=""><figcaption></figcaption></figure>

检查任何已配置的锁定、重试限制和延迟设置。

这些控制措施可降低因重复尝试 PIN 而暴露的风险。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FcclelvAOm6UmrvflwDKN%2Fimage.png?alt=media&amp;token=4a96870d-a219-4b69-91ee-5cfd3e724d6b" alt=""><figcaption></figcaption></figure>

### 报告发现

记录 WPS 状态和可用的防护措施。

不要在报告中包含可用的 PIN 或网络密码。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FF5JPOge4W3zp1FeTs330%2Fimage.png?alt=media&amp;token=8040caf3-0f8d-415b-a5d3-dac84eb09984" alt=""><figcaption></figcaption></figure>

### 修复 WPS 暴露风险

除非有记录在案的业务需求，否则应在生产网络上禁用 WPS。

应用最新固件并替换默认管理凭据。

尽可能使用 WPA3。否则应强制使用长且唯一的 Wi‑Fi 密码短语。


---

# 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/hacking-wifi/wpa-wpa2-psk-network-attacks/wps/wps-attacks.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.
