> 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-vulnerabilities/json-web-token-jwt-attack/jwt-pivoting-user-pentesting-web.md).

# JWT-Benutzer-Pivoting

## JWT-Null:

Wir authentifizieren uns als ein **normaler Benutzer** „user“ mit Rechten *Gast*:

<figure><img src="/files/e59cd55f10818f017ab91d064103c269d5cd349b" alt="" width="563"><figcaption></figcaption></figure>

Wir beobachten, dass wir ein **Session-Cookie** in JWT:

<figure><img src="/files/5d80046e8248fbc72be3c6a53a7bd72d4f17953f" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/68f82668630501b15157982a0878e7923e990aa2" alt=""><figcaption></figcaption></figure>

Von dem **Terminal**, übersetzen wir in **base64** den „Header“ und den „Payload“, indem wir die Nummernidentifikation ändern, dann entfernen wir die „Signatur prüfen“:

<figure><img src="/files/68a620cf336d4d5a88f5b1f900501d354922be51" alt=""><figcaption></figcaption></figure>

Wir fügen die neue **Session-Cookie** und erhalten Rechte *normal*:

<figure><img src="/files/1e45dac6f72b0e925b5f6f6cc2d4183a799c10cc" alt=""><figcaption></figcaption></figure>

## JWT-Geheimnis

Beim Testen der JWT-Null-Methode würde dies **nicht funktionieren** und der Versuch würde scheitern.

<figure><img src="/files/c2cf5a81abddadc4c7383812b75d2ad44d7e61f5" alt="" width="563"><figcaption></figcaption></figure>

Die Idee wäre, Passwörter im **Signatur prüfen**, mit Brute-Force oder etwas Reverse Engineering zu versuchen, um das Cookie zu erhalten:

<figure><img src="/files/030b87549ae1a6b72328f9710aa1941a191ce99f" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/784e8fae961e53104432894f41d60f9850ce65f8" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hacking-notes.jord4n.pro/de/web-vulnerabilities/json-web-token-jwt-attack/jwt-pivoting-user-pentesting-web.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
