> 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/fr/web/xss/angularjs-sandbox-escape-with-csp.md).
# Évasion du bac à sable AngularJS avec CSP
Notes sur l’évasion du bac à sable AngularJS avec CSP pour les laboratoires PortSwigger Web Security Academy, y compris le flux de travail d’exploitation, les tests de charge utile, la validation avec Burp Suite et le contexte de remédiation.
### XSS réfléchi avec échappement du bac à sable AngularJS et CSP
Réalisez une attaque de cross-site scripting réfléchi qui contourne la Content Security Policy, s'échappe du bac à sable AngularJS et s'exécute `alert(document.cookie)`.
**Commentaires**/ Le site utilise une politique CSP qui empêche l'exécution de scripts depuis un domaine externe :
```javascript
default-src 'self'; script-src 'self'; style-src 'unsafe-inline' 'self'
```
En consultant la fiche mémo PortSwigger, nous identifions un vecteur AngularJS fonctionnel qui force l'évaluation via un `orderBy` filtre appliqué à la `$event.composedPath()` événement.
* Pour déclencher une alerte :
```javascript
```
* Pour afficher la valeur de `document.cookie`:
```javascript
```
Exemple d'URL construite pour livrer la charge utile et forcer l'exécution du côté de la victime :
```javascript
```
---
# 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/fr/web/xss/angularjs-sandbox-escape-with-csp.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)