Difference between revisions of "XSS in error pages"
|Line 7:||Line 7:|
creating dynamiac web pages it's easy to make a mistake. If generated page depends on entered data (e.g.
URI, HTTP headers etc.) and these data are not filtered enough it is possible that it can be exploited using
URI, HTTP headers etc.) and these data are not filtered enoughit is possible that it can be exploited using
Revision as of 08:17, 15 September 2008
ASDR Table of Contents
While creating dynamiac web pages it's easy to make a mistake. If a generated page depends on entered data (e.g. URI, HTTP headers etc.) and these data are not filtered enough, it is possible that it can be exploited using XSS technique.
Let's assume that we have an error page, which is handling requests for a non existing pages. Classic 404 error page. We may use the code below as an example to inform user about what specific page is missing:
<html> <body> <? php print "Not found: " . urldecode($_SERVER["REQUEST_URI"]); ?> </body> </html>
Let's see how does it work:
In response we got:
Not found: /file_which_not_exist
Now we will try to force the error page to include our code:
The result is:
We have successfully injected the code, our XSS! What does it mean? E.g. that we may try to steal the cookies. Problems which may occur using XSS techique are:
- escaping data entered by the user (e.g. character " after escaping will be \"),
- maximum length of the URI, which HTTP server will accept.
Related Threat Agents