The value of the returnurl request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 94c72"style%3d"x%3aexpression(alert(1))"a0da7569a1a was submitted in the returnurl parameter. This input was echoed as 94c72"style="x:expression(alert(1))"a0da7569a1a in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Issue background
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.
Request
GET /login/signin.aspx?returnurl=http%3a%2f%2fwww.silverlight.net%2fgetstarted%2fdefault.aspx94c72"style%3d"x%3aexpression(alert(1))"a0da7569a1a HTTP/1.1 Host: login.silverlight.net 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: omniID=1298950646238_fd2a_b49d_f334_6636d557aa57; s_cc=true; s_sq=%5B%5BB%5D%5D
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
<head><title> Sign I ...[SNIP]... <a href="https://login.silverlight.net/login/createuser.aspx?returnurl=http://www.silverlight.net/getstarted/default.aspx94c72"style="x:expression(alert(1))"a0da7569a1a"> ...[SNIP]...
2. SSL cookie without secure flag setpreviousnext There are 2 instances of this issue:
If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.
Issue remediation
The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.
The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /login/createuser.aspx?returnurl=http%3a%2f%2fwww.silverlight.net%2fgetstarted%2fdefault.aspx HTTP/1.1 Host: login.silverlight.net 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: omniID=1298950646238_fd2a_b49d_f334_6636d557aa57; s_cc=true; s_sq=%5B%5BB%5D%5D
Response
HTTP/1.1 200 OK Cache-Control: private Content-Type: text/html; charset=utf-8 Vary: Accept-Encoding Server: Microsoft-IIS/7.0 Set-Cookie: ASP.NET_SessionId=euelny55tr4xfdmc04aeqi55; path=/; HttpOnly X-AspNet-Version: 2.0.50727 Set-Cookie: forums.ReturnUrl=http://www.silverlight.net/getstarted/default.aspx; domain=login.silverlight.net; expires=Mon, 21-Mar-2011 02:13:01 GMT; path=/ X-Powered-By: ASP.NET X-Powered-By: ASP.NET Date: Mon, 21 Mar 2011 02:03:01 GMT Content-Length: 9091
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /login/signin.aspx?returnurl=http%3a%2f%2fwww.silverlight.net%2fgetstarted%2fdefault.aspx HTTP/1.1 Host: login.silverlight.net 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: omniID=1298950646238_fd2a_b49d_f334_6636d557aa57; s_cc=true; s_sq=%5B%5BB%5D%5D
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The following problems were identified with the server's SSL certificate:
The server's certificate is not valid for the server's hostname.
The server's certificate is not trusted.
The server presented the following certificates:
Server certificate
Issued to:
CN=*.silverlight.net
Issued by:
Microsoft Secure Server Authority
Valid from:
Mon Jun 28 18:33:00 CDT 2010
Valid to:
Tue Jun 28 18:33:00 CDT 2011
Certificate chain #1
Issued to:
CN=Microsoft Secure Server Authority,DC=redmond,DC=corp,DC=microsoft,DC=com
Issued by:
CN=Microsoft Internet Authority
Valid from:
Wed May 19 17:13:30 CDT 2010
Valid to:
Mon May 19 17:23:30 CDT 2014
Certificate chain #2
Issued to:
CN=Microsoft Internet Authority
Issued by:
GTE CyberTrust Global Root
Valid from:
Wed Apr 14 13:12:26 CDT 2010
Valid to:
Sat Apr 14 13:12:14 CDT 2018
Certificate chain #3
Issued to:
GTE CyberTrust Global Root
Issued by:
GTE CyberTrust Global Root
Valid from:
Wed Aug 12 19:29:00 CDT 1998
Valid to:
Mon Aug 13 18:59:00 CDT 2018
Issue background
SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.
It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.4. Cross-domain Referer leakagepreviousnext There are 2 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 /login/createuser.aspx?returnurl=http%3a%2f%2fwww.silverlight.net%2fgetstarted%2fdefault.aspx HTTP/1.1 Host: login.silverlight.net 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: omniID=1298950646238_fd2a_b49d_f334_6636d557aa57; s_cc=true; s_sq=%5B%5BB%5D%5D
Response
HTTP/1.1 200 OK Cache-Control: private Content-Type: text/html; charset=utf-8 Vary: Accept-Encoding Server: Microsoft-IIS/7.0 Set-Cookie: ASP.NET_SessionId=euelny55tr4xfdmc04aeqi55; path=/; HttpOnly X-AspNet-Version: 2.0.50727 Set-Cookie: forums.ReturnUrl=http://www.silverlight.net/getstarted/default.aspx; domain=login.silverlight.net; expires=Mon, 21-Mar-2011 02:13:01 GMT; path=/ X-Powered-By: ASP.NET X-Powered-By: ASP.NET Date: Mon, 21 Mar 2011 02:03:01 GMT Content-Length: 9091
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
<head><title> Create ...[SNIP]... <p class="no_lines"> <a href="https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=11&ct=1300672981&rver=6.0.5276.0&wp=LBI_SSL&wreply=https:%2F%2Flogin.silverlight.net%2Flogin%2Fcreateuser.aspx%3Freturnurl%3Dhttp:%2F%2Fwww.silverlight.net%2Fgetstarted%2Fdefault.aspx&lc=1033&id=265631">Sign in</a> ...[SNIP]... <p class="no_lines"><a id="idPPScarab" href="https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=11&ct=1300672981&rver=6.0.5276.0&wp=LBI_SSL&wreply=https:%2F%2Flogin.silverlight.net%2Flogin%2Fcreateuser.aspx%3Freturnurl%3Dhttp:%2F%2Fwww.silverlight.net%2Fgetstarted%2Fdefault.aspx&lc=1033&id=265631"><img src="https://www.passportimages.com/1033/signin.gif" class="PassportSignIn" alt="Sign in to Windows Live ID" style="border-style:none" id="idSI"/></a> ...[SNIP]...
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
<head><title> Sign I ...[SNIP]... <p class="no_lines"><a href="https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=11&ct=1300672984&rver=6.0.5276.0&wp=LBI_SSL&wreply=https:%2F%2Flogin.silverlight.net%2Flogin%2Fsignin.aspx%3Freturnurl%3Dhttp:%2F%2Fwww.silverlight.net%2Fgetstarted%2Fdefault.aspx&lc=1033&id=265631">Sign in</a> ...[SNIP]... </p> <a id="idPPScarab" href="https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=11&ct=1300672984&rver=6.0.5276.0&wp=LBI_SSL&wreply=https:%2F%2Flogin.silverlight.net%2Flogin%2Fsignin.aspx%3Freturnurl%3Dhttp:%2F%2Fwww.silverlight.net%2Fgetstarted%2Fdefault.aspx&lc=1033&id=265631"><img src="https://www.passportimages.com/1033/signin.gif" class="PassportSignIn" alt="Sign in to Windows Live ID" style="border-style:none" id="idSI"/></a> ...[SNIP]... <p class="link_not_member">If you would rather use Windows Live ID to sign-in, click <a href="https://login.live.com/login.srf?wa=wsignin1.0&rpsnv=11&ct=1300672984&rver=6.0.5276.0&wp=LBI_SSL&wreply=https:%2F%2Flogin.silverlight.net%2Flogin%2Fsignin.aspx%3Freturnurl%3Dhttp:%2F%2Fwww.silverlight.net%2Fgetstarted%2Fdefault.aspx&lc=1033&id=265631">here</a> ...[SNIP]...
5. Cookie without HttpOnly flag setpreviousnext There are 2 instances of this issue:
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /login/createuser.aspx?returnurl=http%3a%2f%2fwww.silverlight.net%2fgetstarted%2fdefault.aspx HTTP/1.1 Host: login.silverlight.net 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: omniID=1298950646238_fd2a_b49d_f334_6636d557aa57; s_cc=true; s_sq=%5B%5BB%5D%5D
Response
HTTP/1.1 200 OK Cache-Control: private Content-Type: text/html; charset=utf-8 Vary: Accept-Encoding Server: Microsoft-IIS/7.0 Set-Cookie: ASP.NET_SessionId=euelny55tr4xfdmc04aeqi55; path=/; HttpOnly X-AspNet-Version: 2.0.50727 Set-Cookie: forums.ReturnUrl=http://www.silverlight.net/getstarted/default.aspx; domain=login.silverlight.net; expires=Mon, 21-Mar-2011 02:13:01 GMT; path=/ X-Powered-By: ASP.NET X-Powered-By: ASP.NET Date: Mon, 21 Mar 2011 02:03:01 GMT Content-Length: 9091
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /login/signin.aspx?returnurl=http%3a%2f%2fwww.silverlight.net%2fgetstarted%2fdefault.aspx HTTP/1.1 Host: login.silverlight.net 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: omniID=1298950646238_fd2a_b49d_f334_6636d557aa57; s_cc=true; s_sq=%5B%5BB%5D%5D
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The following email address was disclosed in the response:
id@Ss.tc
Issue background
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
Request
GET /resources/script/omniture/omniture.combined.min.js HTTP/1.1 Host: login.silverlight.net Connection: keep-alive Referer: https://login.silverlight.net/login/createuser.aspx?returnurl=http%3a%2f%2fwww.silverlight.net%2fgetstarted%2fdefault.aspx 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: */* 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: omniID=1298950646238_fd2a_b49d_f334_6636d557aa57; s_cc=true; s_sq=%5B%5BB%5D%5D; ASP.NET_SessionId=u3acpz45cgy01b45m00wgje0; forums.ReturnUrl=http://www.silverlight.net/getstarted/default.aspx
Response
HTTP/1.1 200 OK Content-Type: application/x-javascript Last-Modified: Tue, 21 Dec 2010 00:19:52 GMT Accept-Ranges: bytes ETag: "b2459c9a4a0cb1:0" Vary: Accept-Encoding Server: Microsoft-IIS/7.0 X-Powered-By: ASP.NET X-Powered-By: ASP.NET Date: Mon, 21 Mar 2011 02:02:19 GMT Content-Length: 23800
...var s_account = "msstoslvnet"; var omniGuidPath = "://www.iis.net/omniture/analyticsid.aspx"; if (window.location.hostname.toLowerCase().indexOf("silverlight.net") == -1) { var s2 = s_account.split ...[SNIP]... )`2'';@w=s.vs(sed)`5trk`F@w)#4=s.mr($1,(vt#Rt`avt)`n+s.hav()+q+(qs?qs:s.rq(^4)),0,id,ta);qs`i;`Xm('t')`5s.p_r)s.p_r(`U`b`i}^G(qs);^b`t(@v;`p@v`M^2,`H$I1',vb`G''`5#F)`I^z$z=`I^zeo=`I^z`W`q=`I^z`W^c`i`5!id@Ss.tc@1tc=1;s.flush`T()}`2#4`9tl`0o,t,n,vo`1;@X=$7o`U`W^c=t;s.`W`q=n;s.t(@v}`5pg){`I^zco`0o){`L^t\"_\",1,#U`2$7o)`9wd^zgs`0u$S`L^t#71,#U`2s.t()`9wd^zdc`0u$S`L^t#7#U`2s.t()}}@A=(`I`P`g`8`4$5s@p0`Ud=^9;s.b=s. ...[SNIP]...
Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.
Issue remediation
The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:
Cache-control: no-store
Pragma: no-cache
Request
GET /login/createuser.aspx?returnurl=http%3a%2f%2fwww.silverlight.net%2fgetstarted%2fdefault.aspx HTTP/1.1 Host: login.silverlight.net 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: omniID=1298950646238_fd2a_b49d_f334_6636d557aa57; s_cc=true; s_sq=%5B%5BB%5D%5D
Response
HTTP/1.1 200 OK Cache-Control: private Content-Type: text/html; charset=utf-8 Vary: Accept-Encoding Server: Microsoft-IIS/7.0 Set-Cookie: ASP.NET_SessionId=euelny55tr4xfdmc04aeqi55; path=/; HttpOnly X-AspNet-Version: 2.0.50727 Set-Cookie: forums.ReturnUrl=http://www.silverlight.net/getstarted/default.aspx; domain=login.silverlight.net; expires=Mon, 21-Mar-2011 02:13:01 GMT; path=/ X-Powered-By: ASP.NET X-Powered-By: ASP.NET Date: Mon, 21 Mar 2011 02:03:01 GMT Content-Length: 9091
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
<head><title> Create ...[SNIP]...
Report generated by XSS.CX at Sun Mar 20 21:05:43 CDT 2011.