XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, Bugzilla Version 3.2.3

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

1.1. https://vulnerable.bugzilla.version.3.2.3.host/ next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/

Issue detail

The page contains a form with the following action URL:

https://vulnerable.bugzilla.version.3.2.3.host/index.cgi

The form contains the following password field with autocomplete enabled:

Bugzilla_password

Request

GET / HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/show_bug.cgi?id=49235
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:35:34 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 8208

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Bugzilla Main Page</title>

<link rel="Top" hre
...[SNIP]...
</ul><form name="login" action="https://bugs.webkit.org/index.cgi" method="POST">
<table id="login-small">
...[SNIP]...
<td>
<input type="password" size="20" id="Bugzilla_password" name="Bugzilla_password">
</td>
...[SNIP]...

1.2. https://vulnerable.bugzilla.version.3.2.3.host/enter_bug.cgi previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/enter_bug.cgi

Issue detail

The page contains a form with the following action URL:

https://vulnerable.bugzilla.version.3.2.3.host/enter_bug.cgi

The form contains the following password field with autocomplete enabled:

Bugzilla_password

Request

GET /enter_bug.cgi?product=Security HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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
Date: Wed, 25 May 2011 01:08:40 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 6244

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Log in to Bugzilla</title>

<link rel="Top" hre
...[SNIP]...
</p>

<form name="login" action="enter_bug.cgi" method="POST">
<table>
...[SNIP]...
<td>
<input type="password" size="35" id="Bugzilla_password" name="Bugzilla_password">
</td>
...[SNIP]...

2. Cross-site scripting (reflected) previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/show_bug.cgi

Issue detail

The value of the BUGLIST cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ca8d0"><script>alert(1)</script>01d8e71badd was submitted in the BUGLIST cookie. 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 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.

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 /show_bug.cgi?id=49235 HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/buglist.cgi?keywords=XSSAuditor&resolution=---
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895ca8d0"><script>alert(1)</script>01d8e71badd

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:10:02 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 31858

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Bug 49235 – Searching for ...return false.
...[SNIP]...
<link rel="Last" href="show_bug.cgi?id=27895ca8d0"><script>alert(1)</script>01d8e71badd">
...[SNIP]...

3. SSL cookie without secure flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/buglist.cgi

Issue detail

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

LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT
BUGLIST=29278%3A49235%3A27639%3A27895; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Issue background

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.

Request

GET /buglist.cgi?keywords=XSSAuditor&resolution=--- HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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
Date: Wed, 25 May 2011 01:08:37 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Content-disposition: inline; filename="bugs-2011-05-24.html"
Set-Cookie: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT
Set-Cookie: BUGLIST=29278%3A49235%3A27639%3A27895; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 17709

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Bug List</title>

<link rel="Top" href="https:/
...[SNIP]...

4. Cookie without HttpOnly flag set previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/buglist.cgi

Issue detail

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

LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT
BUGLIST=29278%3A49235%3A27639%3A27895; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT

The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their 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

5. Email addresses disclosed previous next
There are 9 instances of this issue:

/createaccount.cgi
/js/field.js
/js/productform.js
/js/util.js
/skins/contrib/Dusk/buglist.css
/skins/contrib/Dusk/global.css
/skins/standard/buglist.css
/skins/standard/global.css
/skins/standard/index.css

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).

5.1. https://vulnerable.bugzilla.version.3.2.3.host/createaccount.cgi previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/createaccount.cgi

Issue detail

The following email address was disclosed in the response:

admin@webkit.org

Request

GET /createaccount.cgi HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/enter_bug.cgi
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:37:04 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 5872

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>
Create a new Bugzilla account</title>

<link
...[SNIP]...
<a href="mailto:admin@webkit.org">admin@webkit.org</a>
...[SNIP]...

5.2. https://vulnerable.bugzilla.version.3.2.3.host/js/field.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/js/field.js

Issue detail

The following email addresses were disclosed in the response:

guy.pyrzak@gmail.com
mkanat@bugzilla.org

Request

GET /js/field.js HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/buglist.cgi?keywords=XSSAuditor&resolution=---
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:08:41 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Sat, 17 Oct 2009 22:49:31 GMT
ETag: "39d8-47629535a34c0"
Accept-Ranges: bytes
Cache-Control: max-age=32000000
Expires: Tue, 29 May 2012 10:02:01 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: application/javascript
Content-Length: 14808

/* The contents of this file are subject to the Mozilla Public
* License Version 1.1 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of
* t
...[SNIP]...
<mkanat@bugzilla.org>
...[SNIP]...
<guy.pyrzak@gmail.com>
...[SNIP]...

5.3. https://vulnerable.bugzilla.version.3.2.3.host/js/productform.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/js/productform.js

Issue detail

The following email address was disclosed in the response:

kiko@async.com.br

Request

GET /js/productform.js HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/request.cgi
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:37:14 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Fri, 03 Jul 2009 02:14:27 GMT
ETag: "3bd2-46dc3b73b26c0"
Accept-Ranges: bytes
Cache-Control: max-age=32000000
Expires: Tue, 29 May 2012 10:30:34 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: application/javascript
Content-Length: 15314

/* The contents of this file are subject to the Mozilla Public
* License Version 1.1 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of
* t
...[SNIP]...
<kiko@async.com.br>
...[SNIP]...

5.4. https://vulnerable.bugzilla.version.3.2.3.host/js/util.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/js/util.js

Issue detail

The following email addresses were disclosed in the response:

christopher@aillon.com
mkanat@bugzilla.org

Request

GET /js/util.js HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/buglist.cgi?keywords=XSSAuditor&resolution=---
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:08:39 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Fri, 03 Jul 2009 02:14:27 GMT
ETag: "f3a-46dc3b73b26c0"
Accept-Ranges: bytes
Cache-Control: max-age=32000000
Expires: Tue, 29 May 2012 10:01:59 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: application/javascript
Content-Length: 3898

/* ***** BEGIN LICENSE BLOCK *****
* Version: MPL 1.1
*
* The contents of this file are subject to the Mozilla Public License Version
* 1.1 (the "License"); you may not use this file except in com
...[SNIP]...
<mkanat@bugzilla.org>
...[SNIP]...
<christopher@aillon.com>
...[SNIP]...

5.5. https://vulnerable.bugzilla.version.3.2.3.host/skins/contrib/Dusk/buglist.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/skins/contrib/Dusk/buglist.css

Issue detail

The following email addresses were disclosed in the response:

bugzilla@glob.com.au
mschrag@pobox.com
wurblzap@gmail.com

Request

GET /skins/contrib/Dusk/buglist.css HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/buglist.cgi?keywords=XSSAuditor&resolution=---
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: text/css,*/*;q=0.1
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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:08:49 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Fri, 03 Jul 2009 02:14:27 GMT
ETag: "3b3-46dc3b73b26c0"
Accept-Ranges: bytes
Cache-Control: max-age=32000000
Expires: Tue, 29 May 2012 10:02:09 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: text/css
Content-Length: 947

/* The contents of this file are subject to the Mozilla Public
* License Version 1.1 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of

...[SNIP]...
<mschrag@pobox.com>
...[SNIP]...
<bugzilla@glob.com.au>
...[SNIP]...
<wurblzap@gmail.com>
...[SNIP]...

5.6. https://vulnerable.bugzilla.version.3.2.3.host/skins/contrib/Dusk/global.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/skins/contrib/Dusk/global.css

Issue detail

The following email addresses were disclosed in the response:

LpSolit@gmail.com
bugzilla@glob.com.au
mschrag@pobox.com
wurblzap@gmail.com

Request

GET /skins/contrib/Dusk/global.css HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/buglist.cgi?keywords=XSSAuditor&resolution=---
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: text/css,*/*;q=0.1
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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:08:41 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Fri, 03 Jul 2009 02:14:27 GMT
ETag: "1263-46dc3b73b26c0"
Accept-Ranges: bytes
Cache-Control: max-age=32000000
Expires: Tue, 29 May 2012 10:02:01 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: text/css
Content-Length: 4707

/* The contents of this file are subject to the Mozilla Public
* License Version 1.1 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of

...[SNIP]...
<mschrag@pobox.com>
...[SNIP]...
<bugzilla@glob.com.au>
...[SNIP]...
<wurblzap@gmail.com>
...[SNIP]...
<LpSolit@gmail.com>
...[SNIP]...

5.7. https://vulnerable.bugzilla.version.3.2.3.host/skins/standard/buglist.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/skins/standard/buglist.css

Issue detail

The following email address was disclosed in the response:

myk@mozilla.org

Request

GET /skins/standard/buglist.css HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/buglist.cgi?keywords=XSSAuditor&resolution=---
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: text/css,*/*;q=0.1
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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:08:45 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Fri, 03 Jul 2009 02:14:27 GMT
ETag: "6fb-46dc3b73b26c0"
Accept-Ranges: bytes
Cache-Control: max-age=32000000
Expires: Tue, 29 May 2012 10:02:05 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: text/css
Content-Length: 1787

/* The contents of this file are subject to the Mozilla Public
* License Version 1.1 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of

...[SNIP]...
<myk@mozilla.org>
...[SNIP]...

5.8. https://vulnerable.bugzilla.version.3.2.3.host/skins/standard/global.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/skins/standard/global.css

Issue detail

The following email addresses were disclosed in the response:

bugzilla@glob.com.au
kiko@async.com.br
light@rathedg.com
vitaly@rathedg.com
wurblzap@gmail.com

Request

GET /skins/standard/global.css HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/buglist.cgi?keywords=XSSAuditor&resolution=---
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: text/css,*/*;q=0.1
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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:08:38 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Fri, 03 Jul 2009 02:14:27 GMT
ETag: "20dc-46dc3b73b26c0"
Accept-Ranges: bytes
Cache-Control: max-age=32000000
Expires: Tue, 29 May 2012 10:01:58 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: text/css
Content-Length: 8412

/* The contents of this file are subject to the Mozilla Public
* License Version 1.1 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of

...[SNIP]...
<bugzilla@glob.com.au>
...[SNIP]...
<kiko@async.com.br>
...[SNIP]...
<vitaly@rathedg.com>
...[SNIP]...
<light@rathedg.com>
...[SNIP]...
<wurblzap@gmail.com>
...[SNIP]...

5.9. https://vulnerable.bugzilla.version.3.2.3.host/skins/standard/index.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/skins/standard/index.css

Issue detail

The following email address was disclosed in the response:

vitaly@rathedg.com

Request

GET /skins/standard/index.css HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Accept: text/css,*/*;q=0.1
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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:35:36 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Fri, 03 Jul 2009 02:13:45 GMT
ETag: "6b6-46dc3b4ba4840"
Accept-Ranges: bytes
Cache-Control: max-age=32000000
Expires: Tue, 29 May 2012 10:28:56 GMT
Vary: Accept-Encoding
Connection: close
Content-Type: text/css
Content-Length: 1718

/* The contents of this file are subject to the Mozilla Public
* License Version 1.1 (the "License"); you may not use this file
* except in compliance with the License. You may obtain a copy of

...[SNIP]...
<vitaly@rathedg.com>
...[SNIP]...

6. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/buglist.cgi

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: vulnerable.bugzilla.version.3.2.3.host

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:08:39 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Last-Modified: Wed, 06 Feb 2008 22:40:55 GMT
ETag: "2c-445850cd38bc0"
Accept-Ranges: bytes
Content-Length: 44
Vary: Accept-Encoding
Connection: close
Content-Type: text/plain

User-agent: *
Allow: /index.cgi
Disallow: /

7. Cacheable HTTPS response previous next
There are 8 instances of this issue:

/
/attachment.cgi
/buglist.cgi
/createaccount.cgi
/enter_bug.cgi
/report.cgi
/request.cgi
/show_bug.cgi

Issue description

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

7.1. https://vulnerable.bugzilla.version.3.2.3.host/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/

Request

Response

7.2. https://vulnerable.bugzilla.version.3.2.3.host/attachment.cgi previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/attachment.cgi

Request

GET /attachment.cgi?id=73356&action=edit HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
Referer: https://vulnerable.bugzilla.version.3.2.3.host/show_bug.cgi?id=49235
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:09:37 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 16566

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>
Attachment 73356 Details for Bug 49235</title
...[SNIP]...

7.3. https://vulnerable.bugzilla.version.3.2.3.host/buglist.cgi previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/buglist.cgi

Request

Response

7.4. https://vulnerable.bugzilla.version.3.2.3.host/createaccount.cgi previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/createaccount.cgi

Request

Response

7.5. https://vulnerable.bugzilla.version.3.2.3.host/enter_bug.cgi previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/enter_bug.cgi

Request

Response

7.6. https://vulnerable.bugzilla.version.3.2.3.host/report.cgi previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/report.cgi

Request

GET /report.cgi HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:37:09 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 5485

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Reporting and Charting Kitchen</title>

<link r
...[SNIP]...

7.7. https://vulnerable.bugzilla.version.3.2.3.host/request.cgi previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/request.cgi

Request

GET /request.cgi HTTP/1.1
Host: vulnerable.bugzilla.version.3.2.3.host
Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 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: LASTORDER=bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id; BUGLIST=29278%3A49235%3A27639%3A27895

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:37:11 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 10559

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Request Queue</title>

<link rel="Top" href="ht
...[SNIP]...

7.8. https://vulnerable.bugzilla.version.3.2.3.host/show_bug.cgi previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/show_bug.cgi

Request

Response

HTTP/1.1 200 OK
Date: Wed, 25 May 2011 01:09:26 GMT
Server: Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/1.0.0c DAV/2 mod_python/3.3.1 Python/2.6.6 PHP/5.2.17
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 31729

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Bug 49235 – Searching for ...return false.
...[SNIP]...

8. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://vulnerable.bugzilla.version.3.2.3.host
Path:	/

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:	*.webkit.org
Issued by:	Entrust Certification Authority - L1C
Valid from:	Mon Jan 31 17:14:55 CST 2011
Valid to:	Tue Jan 29 03:39:19 CST 2013

Certificate chain #1

Issued to:	Entrust Certification Authority - L1C
Issued by:	Entrust.net Certification Authority (2048)
Valid from:	Thu Dec 10 14:43:54 CST 2009
Valid to:	Tue Dec 10 15:13:54 CST 2019

Certificate chain #2

Issued to:	Entrust.net Certification Authority (2048)
Issued by:	Entrust.net Certification Authority (2048)
Valid from:	Fri Dec 24 11:50:51 CST 1999
Valid to:	Tue Jul 24 09:15:12 CDT 2029

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.

Report generated by XSS.CX at Wed May 25 13:32:13 CDT 2011.