> 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/path-traversal/path-traversal-sequences-stripped-without-recursive-processing.md). # Séquences de traversée de chemin supprimées sans traitement récursif Notes sur les séquences de traversée de chemin supprimées sans traitement récursif pour les laboratoires de la PortSwigger Web Security Academy, incluant le workflow d’exploitation, les tests de payloads, la validation dans Burp Suite et la remédiation ### Traversée de chemin de fichier, séquences de traversée supprimées de manière non récursive Un payload fonctionnel utilise donc des chaînes telles que : Étant donné que le code supprime `../` les occurrences directement, il est possible de contourner ce mécanisme en **doublant les points et les barres obliques**. Lorsque la séquence filtrée est supprimée, il en reste toujours une partie exploitable. L'objectif est de récupérer le contenu du **/etc/passwd** fichier. L'application supprime les séquences de traversée (`../`) fournies par l'utilisateur, mais le fait **de manière non récursive**. ```bash ....//....//....//....//etc/passwd ``` Exemple avec **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/fr/web/path-traversal/path-traversal-sequences-stripped-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.