Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 98348 - www-apps/bugzilla 2.18.1 Security Advisory
Summary: www-apps/bugzilla 2.18.1 Security Advisory
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Gentoo Security
URL: http://www.bugzilla.org/security/2.18.1/
Whiteboard: A4 [glsa]
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-08 06:21 UTC by Renat Lumpau (RETIRED)
Modified: 2005-07-13 13:41 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Renat Lumpau (RETIRED) gentoo-dev 2005-07-08 06:21:05 UTC
Advisory text below. Also note this email to announce@bugzilla.org:

Date: Fri, 08 Jul 2005 05:18:45 -0400                                           
From: David Miller <justdave@bugzilla.org>
Subject: Re: [ANN] Release of Bugzilla 2.18.2 and 2.20rc1
Max Kanat-Alexander wrote:                                                      
                                                                                
> We are also releasing a bug-fix release for the 2.18 series, 2.18.2.          
> The 2.18 series is recommended for users in production environments.          
> All users of the 2.18 series are recommended to upgrade to 2.18.2 as          
> soon as possible.                                                             
                                                                                
The 2.18.2 release has a broken query page due to a checkin from bug            
268146 just prior to the release.                                               
                                                                                
See https://bugzilla.mozilla.org/show_bug.cgi?id=268146                         
                                                                                
You can get it working by editing the file "Bugzilla/CGI.pm" and 
removing line 193, which looks like the following:                              
                                                                                
    $paramhash{'-domain'} = Param('cookiedomain') if Param('cookiedomain');     
                                                                                
We'll get a 2.18.3 out tomorrow that corrects this.                             
                                                                                
In the mean time, our deepest apologies to anyone who's already                 
installed it.  Various people are being chastised as we speak for               
failing to test sufficiently prior to release and we're already                 
discussing ways to enhance our automated testing to catch this sort of          
thing.


=======================================================
July 7, 2005

Summary
=======

Bugzilla is a Web-based bug-tracking system, used by a large number of
software projects.

This advisory covers two security bugs that have recently been
discovered and fixed in the Bugzilla code:

 + 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 Bugzilla installations are advised to upgrade to the latest stable
version of Bugzilla, 2.18.2.

Development snapshots of 2.19 and above are also vulnerable. If you are
using a development snapshot, you should upgrade to the release candidate
(2.20rc1), use CVS to update, or apply the patches from the specific 
bugs listed below.


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

Issue 1
-------
Class:       Unauthorized Bug Change, Information Leak
Versions:    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.
Reference:   https://bugzilla.mozilla.org/show_bug.cgi?id=293159

Issue 2
-------
Class:       Information Leak
Versions:    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.
Reference:   https://bugzilla.mozilla.org/show_bug.cgi?id=292544


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

The fixes for all of the security bugs mentioned in this advisory
are included in the 2.18.2 and 2.20rc1 releases.  Upgrading
to these releases will protect installations from possible exploits
of these issues.

Full release downloads, patches to upgrade Bugzilla from previous
versions, and CVS upgrade instructions are available at:
  http://www.bugzilla.org/download.html

Specific patches for each of the individual issues can be found on the
corresponding bug reports for each issue, at the URL given in the
reference for that issue in the list above.


Credits
=======

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

Fr
Comment 1 Renat Lumpau (RETIRED) gentoo-dev 2005-07-08 06:21:05 UTC
Advisory text below. Also note this email to announce@bugzilla.org:

Date: Fri, 08 Jul 2005 05:18:45 -0400                                           
From: David Miller <justdave@bugzilla.org>
Subject: Re: [ANN] Release of Bugzilla 2.18.2 and 2.20rc1
Max Kanat-Alexander wrote:                                                      
                                                                                
> We are also releasing a bug-fix release for the 2.18 series, 2.18.2.          
> The 2.18 series is recommended for users in production environments.          
> All users of the 2.18 series are recommended to upgrade to 2.18.2 as          
> soon as possible.                                                             
                                                                                
The 2.18.2 release has a broken query page due to a checkin from bug            
268146 just prior to the release.                                               
                                                                                
See https://bugzilla.mozilla.org/show_bug.cgi?id=268146                         
                                                                                
You can get it working by editing the file "Bugzilla/CGI.pm" and 
removing line 193, which looks like the following:                              
                                                                                
    $paramhash{'-domain'} = Param('cookiedomain') if Param('cookiedomain');     
                                                                                
We'll get a 2.18.3 out tomorrow that corrects this.                             
                                                                                
In the mean time, our deepest apologies to anyone who's already                 
installed it.  Various people are being chastised as we speak for               
failing to test sufficiently prior to release and we're already                 
discussing ways to enhance our automated testing to catch this sort of          
thing.


=======================================================
July 7, 2005

Summary
=======

Bugzilla is a Web-based bug-tracking system, used by a large number of
software projects.

This advisory covers two security bugs that have recently been
discovered and fixed in the Bugzilla code:

 + 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 Bugzilla installations are advised to upgrade to the latest stable
version of Bugzilla, 2.18.2.

Development snapshots of 2.19 and above are also vulnerable. If you are
using a development snapshot, you should upgrade to the release candidate
(2.20rc1), use CVS to update, or apply the patches from the specific 
bugs listed below.


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

Issue 1
-------
Class:       Unauthorized Bug Change, Information Leak
Versions:    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.
Reference:   https://bugzilla.mozilla.org/show_bug.cgi?id=293159

Issue 2
-------
Class:       Information Leak
Versions:    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.
Reference:   https://bugzilla.mozilla.org/show_bug.cgi?id=292544


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

The fixes for all of the security bugs mentioned in this advisory
are included in the 2.18.2 and 2.20rc1 releases.  Upgrading
to these releases will protect installations from possible exploits
of these issues.

Full release downloads, patches to upgrade Bugzilla from previous
versions, and CVS upgrade instructions are available at:
  http://www.bugzilla.org/download.html

Specific patches for each of the individual issues can be found on the
corresponding bug reports for each issue, at the URL given in the
reference for that issue in the list above.


Credits
=======

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

Frédéric Buclin
Matthias Versen
Joel Peshkin
Myk Melez

General information about the Bugzilla bug-tracking system can be found
at http://www.bugzilla.org/

Comments and follow-ups can be directed to the
netscape.public.mozilla.webtools newsgroup or the mozilla-webtools
mailing list; http://www.bugzilla.org/support/ has directions for
accessing these forums.
Comment 2 Renat Lumpau (RETIRED) gentoo-dev 2005-07-08 12:57:09 UTC
2.20_rc1 is in Portage, will bump the stable ebuilds to 2.18.3 tomorrow
Comment 3 Renat Lumpau (RETIRED) gentoo-dev 2005-07-09 18:07:51 UTC
Added 2.18.3, marked stable on x86.
Comment 4 Stefan Cornelius (RETIRED) gentoo-dev 2005-07-09 18:17:16 UTC
Thanks for bumping, rl03.
Calling arches - please test 2.18.3 and mark stable. Also called amd64, maybe
you guys want to mark this stable, too. Thanks in advance.
Comment 5 Jason Wever (RETIRED) gentoo-dev 2005-07-10 07:33:26 UTC
Stable on SPARC.
Comment 6 Jory A. Pratt 2005-07-10 14:28:33 UTC
marked stable PPC
Comment 7 Simon Stelling (RETIRED) gentoo-dev 2005-07-11 03:59:02 UTC
thanks, marked stable on amd64 too
Comment 8 Markus Rothe (RETIRED) gentoo-dev 2005-07-11 11:23:30 UTC
stable on ppc64 - sorry for delay :-/
Comment 9 Stefan Cornelius (RETIRED) gentoo-dev 2005-07-11 13:12:22 UTC
Ready for GLSA vote.
Comment 10 Thierry Carrez (RETIRED) gentoo-dev 2005-07-12 00:40:50 UTC
I vote yes. A lot of groups (including ourselves) use bugzilla to store
confidential information, and the summary can be revealing.
Comment 11 Matthias Geerdsen (RETIRED) gentoo-dev 2005-07-12 00:48:43 UTC
/me votes YES too
could be critical information that is revealed
Comment 12 Thierry Carrez (RETIRED) gentoo-dev 2005-07-13 13:41:39 UTC
GLSA 200507-12