> 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/fr/web/ssrf/blind-ssrf-with-out-of-band-detection.md). # SSRF aveugle avec détection hors bande Notes sur le SSRF aveugle avec détection hors bande pour les laboratoires PortSwigger Web Security Academy, y compris le flux de travail d’exploitation, les tests de charge utile, la validation avec Burp Suite et le contexte de remédiation. ### SSRF aveugle avec détection hors bande Ce laboratoire utilise un module d’analyse qui effectue une requête HTTP vers l’URL dans le **Referer** en-tête lorsqu’une page produit est chargée. / Pour résoudre le laboratoire, vous devez utiliser ce comportement pour déclencher une requête vers le serveur public **Burp Collaborator**.

Nous constatons que la page récupère la valeur de l’en-tête Referer. / L’objectif est donc de rediriger cette requête vers notre corps Collaborator. Envoyez simplement une requête contenant un Refererer malveillant, par exemple : ``` Referer: https://ld2xyh6ornbpdovp5ww0sartzk5bt1hq.oastify.com ``` Le serveur effectue alors une requête sortante, qui apparaît dans Burp Collaborator, confirmant le fonctionnement de la SSRF aveugle.

--- # 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/fr/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.