Skip to main content

Google XSS Game - Solving Level 6 (Final)

Level6

Link: https://xss-game.appspot.com/level6

Solution

Host a simple Javascript file which can be fetch through a URL (https). The Javascript file need only to contain an alert() method.
alert("XSS")
Place the URL to the https file right after the # tag of the URL. Use HTTPS instead of https in the URL to the scropt to bypass the check.

Result

Analysis

The vulnerability lies withing how the code handles the value after the # tag.

In the line 45, the value right after the # tag is taken as the gadget name. And then in line 48, this value is directly passed into the includeGadget() method.


And in the includeGadget() method a <script> tag is created [line 18] and the url (gadgetName) parameter value is directly used as the src attribute of the <script> tag [line 28].

This means, we can completly control the src attribute of the <script> tag being created. That is, with this vulnerability we can inject our own Javascript file into the code.

The only hurdle is the security check done in the line 21. But this can be easily by passed due to it's case sensitivity. It blocks any value with https or http. But this filter can be bypassed by using Http, HTtpS and so on since URLs are actualy case insensitive.

Conclusion  

We can inject a URL of our own hosted Javascript file into the webapplications URL after the # tag and the URL should not be using https but anything like HTTPS or HttpS to bypass the regular expression for security checking.

Labels:

Comments

  1. hoangdesuSeptember 4, 2023 at 2:44 PM

    I found another solution. You don't have to host your js file anywhere. Instead just use the base64 encoded data of the alert script. For instance alert('hi'); will be turned into "data:undefined;base64,YWxlcnQoJ2hpJyk7".
    Full working URL: https://xss-game.appspot.com/level6/frame#data:undefined;base64,YWxlcnQoJ2hpJyk7
    Love this series, thanks for the previous solutions 👏

    ReplyDelete

Post a Comment

Popular posts from this blog

Google XSS Game - Solving Level 4

Level 4 Link: https://xss-game.appspot.com/level4 Solution If inserted in the text field 3'); alert('XSS Or if injected directly into the URL using timer query parameter ?timer=3%27)%3b+alert(%27XSS Second solution if inserted in the text field 3')+ alert('XSS Or if injected directly into the URL using timer query parameter ?timer=3%27%29%2Balert%28%27XSS Result Analysis It is obvious the value entered in the textbox is tranfered to the server over the timer parameter in the URL. Lets exmine the code to see how the timer parameter is handled. In the line 21 of the timer.html, the startTimer() method is being called in the onload event. However, the timer parameter is directly passed to the startTimer() method. Lets exmine the network trafic to confirm this. Request with timer=3 The parameter value 3 is directly added to the startTimer() method without any filtering. What we can try to do here is to inject an alert() function to be ex...
Post a Comment
Read more

Configuring Log level and Log file for TOR - KaliLinux

The configuration file for TOR is torrc [1] which is in the path /etc/tor/torrc . You have to enable some configurations in this file manually to enable logging in different log levels. Tor has several log levels: err": something bad just happened, and we can't recover. Tor will exit. "warn": something bad happened, but we're still running. The bad thing might be a bug in the code, some other Tor process doing something unexpected, etc. The operator should examine the message and try to correct the problem. "notice": something the operator will want to know about. "info": something happened (maybe bad, maybe ok), but there's nothing you need to (or can) do about it. "debug": for everything louder than info. It is quite loud indeed. Lets enable "notice" and "debug" and log them into separate files. Find the following section of the config file: The torrc config file log configuration Uncommen...
Post a Comment
Read more