> 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/ssrf/blind-ssrf-with-out-of-band-detection.md).
# SSRF ciego con detección fuera de banda
Notas de SSRF ciego con detección fuera de banda para laboratorios de PortSwigger Web Security Academy, incluido el flujo de explotación, pruebas de payloads, validación con Burp Suite y contexto de remediación.
### SSRF ciego con detección fuera de banda
Este laboratorio utiliza un módulo de análisis que realiza una solicitud HTTP a la URL en el **Referer** encabezado cuando se carga una página de producto. / Para resolver el laboratorio, debes usar este comportamiento para activar una solicitud al servidor público **Burp Collaborator**.
Comprobamos que la página recupera el valor del encabezado Referer. / Por lo tanto, el objetivo es redirigir esta solicitud a nuestro cuerpo de Collaborator.
Solo envía una consulta que contenga un Refererer malicioso, por ejemplo:
```
Referer: https://ld2xyh6ornbpdovp5ww0sartzk5bt1hq.oastify.com
```
El servidor entonces realiza una consulta saliente, que aparece en Burp Collaborator, confirmando el funcionamiento de SSRF ciego.
---
# 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/ssrf/blind-ssrf-with-out-of-band-detection.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.
.png?alt=media)
.png?alt=media)