4.4. Bugzilla Security

Poorly-configured MySQL, Bugzilla, and FTP installations have +> Poorly-configured MySQL, Bugzilla, and FTP installations have given attackers full access to systems in the past. Please take these guidelines seriously, even for Bugzilla machines hidden away behind your firewall. 80% of all computer @@ -131,13 +131,13 @@ VALIGN="TOP" >

Secure your installation. +> Secure your installation.

These instructions must, of necessity, be somewhat vague +> These instructions must, of necessity, be somewhat vague since Bugzilla runs on so many different platforms. If you have refinements of these directions for specific platforms, please submit them to

Ensure you are running at least MysQL version 3.22.32 or +> Ensure you are running at least MysQL version 3.22.32 or newer. Earlier versions had notable security holes and poorly secured default configuration choices.

The MySQL Privilege System until you can recite it from memory!

At the very least, ensure you password the "mysql -u root" +> At the very least, ensure you password the "mysql -u root" account and the "bugs" account, establish grant table rights (consult the Keystone guide in Appendix C: The Bugzilla Database for some easy-to-use details) that do @@ -200,14 +200,14 @@ TARGET="_top" >

Lock down /etc/inetd.conf. Heck, disable inet entirely on +> Lock down /etc/inetd.conf. Heck, disable inet entirely on this box. It should only listen to port 25 for Sendmail and port 80 for Apache.

Do not run Apache as Do not run Apache as "nobody". This will @@ -215,12 +215,12 @@ CLASS="QUOTE" Run it, instead, as a user with a name, set via your httpd.conf file.

"nobody" is a real user on UNIX systems. @@ -259,7 +259,7 @@ CLASS="QUOTE" >

Ensure you have adequate access controls for the +> Ensure you have adequate access controls for the $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/shadow/ directories, as well as the $BUGZILLA_HOME/localconfig and $BUGZILLA_HOME/globals.pl files. The localconfig file @@ -274,12 +274,12 @@ CLASS="QUOTE" bug information to those who may not be allowed to see it.

Bugzilla provides default .htaccess files to protect the +> Bugzilla provides default .htaccess files to protect the most common Apache installations. However, you should verify these are adequate according to the site-wide security policy of your web server, and ensure that the @@ -305,7 +305,7 @@ VALIGN="TOP" details.

If you are using a web server that does not support the +> If you are using a web server that does not support the .htaccess control method, you are at risk!

On Apache, you can use .htaccess files to protect access +> On Apache, you can use .htaccess files to protect access to these directories, as outlined in for adequate protection in your data/ and shadow/ directories.

Note the instructions which follow are Apache-specific. +> Note the instructions which follow are Apache-specific. If you use IIS, Netscape, or other non-Apache web servers, please consult your system documentation for how to secure these files from being transmitted to curious users.

Place the following text into a file named ".htaccess", +> Place the following text into a file named ".htaccess", readable by your web server, in your $BUGZILLA_HOME/data directory.

<Files comments> allow
from all </Files> deny from all

Place the following text into a file named ".htaccess", +> Place the following text into a file named ".htaccess", readable by your web server, in your $BUGZILLA_HOME/ directory.

<Files localconfig> deny
from all </Files> allow from all

Place the following text into a file named ".htaccess", +> Place the following text into a file named ".htaccess", readable by your web server, in your $BUGZILLA_HOME/shadow directory.

deny from all