2.18.1 and 2.19.3 Security Advisory

Thursday, Jul 7th, 2005

Summary
=======

Bugzilla is a Web-based bug-tracking system used by a large number of
software projects. The following security issues have been discovered
in Bugzilla:

* Any user can change a flag on any bug. This also allows the 
  attacker to expose the summary of any bug, even a hidden bug.

* Summaries of private bugs are sometimes exposed under a very rare
  condition if you use MySQL replication.

All affected installations are encouraged to upgrade as soon as
possible.


Vulnerability Details
=====================

Class:       Unauthorized Bug Change, Information Leak
Affected:    2.17.1 - 2.18.1, 2.19.1 - 2.19.3
Description: Any user can change any flag on any bug, even if they don't
             have access to that bug, or even if they can't normally
             make bug changes. This also allows them to expose the
             summary of a bug.
             By manually modifying a link to process_bug.cgi, it is possible
             to change a flag on a bug that you do not have access to,
             because Bugzilla does not validate that the flag you are 
             attempting to change is associated with the bug that you 
             are attempting to change.
             If the attacker makes a flag change which causes the attacker
             to be emailed, the attacker will see the summary of the bug
             in that email.
             If you are using the request_group or grant_group features
             of 2.19, the attacker will be prevented from exploiting
             this security hole if they do not have permission to
             change the flag in the fashion that they are changing it.
References:  https://bugzilla.mozilla.org/show_bug.cgi?id=293159


Class:       Information Leak
Affected:    2.17.1 and above
Description: Bugs are inserted into the database before they are marked
             as private, in Bugzilla code. Thus, MySQL replication can
             lag in between the time that the bug is inserted and when
             it is marked as private (usually less than a second). If
             replication lags at this point, the bug summary will be 
             accessible to all users until replication catches up.
             Also, on a very slow machine, there may be a pause
             longer than a second that allows users to see the title of
             the newly-filed bug.


Vulnerability Solutions
=======================

The fix for these issues is included in the 
releases. Upgrading to a release with the relevant fix will
protect your installation from possible exploits of these issues.

If you are unable to upgrade but would like to patch just the security
vulnerability, there are patches available for the issues at the
"References" URL.

Full release downloads, patches to upgrade Bugzilla from previous
versions, and git upgrade instructions are available at:

  https://www.bugzilla.org/download/


Credits
=======

The Bugzilla team wish to thank the following people for their
assistance in locating, advising us of, and assisting us to fix this
issue:


Issue 1 Reporter: Frédéric Buclin
Issue 1 Fixed by: Frédéric Buclin, Myk Melez


Issue 2 Reporter: Matthias Versen
Issue 2 Fixed by: Frédéric Buclin, Joel Peshkin

General information about the Bugzilla bug-tracking system can be found
at:

  https://www.bugzilla.org/

Comments and follow-ups can be directed to the support-bugzilla mailing list.
https://www.bugzilla.org/support/ has directions for accessing this forum.