> 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/file-path-traversal-traversal-sequences-removed-without-recursive-processing.md). # Secuencias de traversal de ruta de archivos eliminadas sin procesamiento recursivo Notas sobre Secuencias de traversal de ruta de archivos eliminadas sin procesamiento recursivo para los laboratorios de PortSwigger Web Security Academy, incluido el flujo de explotación, pruebas de payload, validación en Burp Suite y a ### Recorrido de rutas de archivo, secuencias de recorrido eliminadas de forma no recursiva Por lo tanto, una carga útil funcional usa cadenas como: Dado que el código elimina `../` las ocurrencias directamente, es posible eludir este mecanismo **duplicando los puntos y las barras**. Cuando se elimina la secuencia filtrada, siempre queda una parte utilizable. El objetivo es recuperar el contenido de **/etc/passwd** . La aplicación elimina las secuencias de recorrido (`../`) proporcionadas por el usuario, pero lo hace **no de forma recursiva**. ```bash ....//....//....//....//etc/passwd ``` Ejemplo con **curl**: {% code overflow="wrap" %} ```bash curl 'https://0ae0005c04ab83ac82531f6d002300a2.web-security-academy.net/image?filename=....//....//....//....//....//etc/passwd' ``` {% 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/path-traversal/file-path-traversal-traversal-sequences-removed-without-recursive-processing.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.