> 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/de/web/path-traversal/path-traversal-with-absolute-path-bypass-when-sequences-are-blocked.md).

# Path Traversal mit Umgehung über den absoluten Pfad, wenn Sequenzen blockiert sind

Notizen zu Path Traversal mit Umgehung über den absoluten Pfad, wenn Sequenzen blockiert sind für die Labs der PortSwigger Web Security Academy, einschließlich Ausnutzungsablauf, Payload-Tests, Burp-Suite-Validierung und Behebu

### Dateipfad-Traversal, Traversal-Sequenzen mit Umgehung über absoluten Pfad blockiert

Die Anwendung blockiert die Traversal-Sequenzen (`../`), behandelt den angegebenen Dateinamen jedoch so, als würde er sich auf ein Standard-Arbeitsverzeichnis beziehen.

Um das Labor zu lösen, stellen Sie einfach den Inhalt von **/etc/passwd** Datei vorhanden sind.

Da die Traversal-Sequenzen gefiltert werden, kann der Mechanismus umgangen werden, indem direkt ein absoluter Pfad angegeben wird:

```bash
/etc/passwd
```

Beispiel mit **curl**:

{% code overflow="wrap" %}

```bash
curl 'https://0ac400440477a34780513f2a000f00a1.web-security-academy.net/image?filename=/etc/passwd'
```

{% endcode %}

<figure><img src="https://2955439919-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8ad6641a1f7bc924302fe9d3ffdc21f856941311%2Fimage%20(251).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/de/web/path-traversal/path-traversal-with-absolute-path-bypass-when-sequences-are-blocked.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.
