I'm testing xss attacks on my own code. The example beneath is a simple box where an user can type whatever he wants. After pressing "test!" button, JS will show the input string into two divs.This is an example I made to explain better my question:
if you try to copy it into a .html file and run it, it will work fine, but if you try to input
<script>alert('xss')</script>, only one alert box will be thrown: the one inside `test-html' div (with html() function).
I really can't understand why this is happening, and also, inspecting the code with firebug gives me this result (after injecting the script)
<body> this is a test <input id="input-test" type="text" name="foo"> <input type="button" value="test!" onclick="testIt();"> <div id="test-html"> </div> <div id="test-innerHTML"> <script> alert('xss') </script> </div> </body>
as you can see
test-html div is empty, and
test-innerhtml div contans the script. Can someone tell me why? Is because html() is more secure against scripts injection or something similar?
Thanks in advance, best regards.
JQuery strips out the script tags, which is why you aren't seeing it append to the dom let alone executing.
To see an explanation of why jquery strips it out, you can see John Resig's reply here: https://forum.jquery.com/topic/jquery-dommanip-script-tag-will-be-removed
Hope this helps
Contrary to what is being said on this page,
jQuery.html() and the many jQuery functions which accept HTML strings as arguments are more prone to DOM-based XSS injection than
innerHTML, as noticed by the OP.
jQuery.html() extracts the
<script> tags, updates the DOM and evaluates the code embedded in the script tags.
As a result, XSS can happen without user interaction even after the DOM is loaded when using
This is very easy to demonstrate.
This will call
While this will not:
var d = document.getElementById('xss'); d.innerHTML = '<script\>alert("XSS");</script\>';
Unfortunately, there are many other code paths (sinks) which lead to calling
eval() in jQuery. The security conscious will probably avoid jQuery altogether, as far as possible.
Note that I do not claim that using innerHTML is an effective defense against XSS. It is not. Passing unescaped data to innerHTML is not safe, as pointed out by @daghan. One should always properly escape data when generating HTML.
yes jquery html won't render script tags
but it isn't more secure
because you can use many other xss payloads such as
<a href> style , expression etc..
As for why the second one is not being executed, it is because dynamically added scripts like that will not be run after the page has been loaded.
But, as @Ben points out, there are a lot of XSS openings when accepting things like that. That said, if the information is being displayed on their own page, they can run any arbitrary code they want on their own machine. The big issue will be if you store this, or send this to other users. Unless you do that, there is no protecting users from themselves in these sorts of regards. Maybe knowing what you're trying to protect against will help.
©2020 All rights reserved.