> 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/access-control/access-control-based-on-the-referer-header.md).
# Control de acceso basado en el encabezado Referer
Notas sobre Control de acceso basado en el encabezado Referer para los laboratorios de PortSwigger Web Security Academy, incluido el flujo de explotación, pruebas de payload, validación en Burp Suite y contexto de mitigación.
### Control de acceso basado en Referer
Este laboratorio aplica un control de acceso a las funciones de administración basado en el encabezado **Referer**. / Primero puedes explorar el panel de administración conectándote con **administrator:admin** credenciales.
Para resolver el laboratorio, debes iniciar sesión con el usuario **wiener:peter** y usar la validación incorrecta del Referer para obtener un rol de administrador.
#### **1. Contexto**
* Cookie de sesión para *wiener*
```bash
cIA2AyZn2GhizvLK7VR8SUCMcdezZcFl
```
* Al intentar cambiar roles sin un encabezado adicional, la aplicación deniega el acceso:
```http
GET /admin-roles?username=wiener&action=upgrade HTTP/2
Host: 0a19008c034b40de834b14e0009a0062.web-security-academy.net
Cookie: session=cIA2AyZn2GhizvLK7VR8SUCMcdezZcFl
```
La respuesta indica que el usuario no tiene los permisos necesarios.
#### **2. Omitiendo la comprobación de Referer**
Si se añade un encabezado **Referer** que apunte a una página de administrador legítima, la aplicación acepta la operación
```bash
Referer: https://0a19008c034b40de834b14e0009a0062.web-security-academy.net/admin
```
Con este encabezado añadido, es posible ascender a wiener y obtener acceso 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/es/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.
