From lpsolit at gmail.com Thu Dec 29 16:46:01 2011 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 29 Dec 2011 17:46:01 +0100 Subject: Security advisory for Bugzilla 4.2rc1, 4.0.3, 3.6.7 and 3.4.13 Message-ID: <4EFC9949.9070607@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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: * When viewing tabular or graphical reports as well as new charts, an XSS vulnerability is possible in debug mode. * The User.offer_account_by_email WebService method lets you create a new user account even if the active authentication method forbids users to create an account. * A CSRF vulnerability in post_bug.cgi and in attachment.cgi could lead to the creation of unwanted bug reports and attachments. All affected installations are encouraged to upgrade as soon as possible. Vulnerability Details ===================== Class: Cross-Site Scripting Versions: 2.17.1 to 3.4.12, 3.5.1 to 3.6.6, 3.7.1 to 4.0.2, 4.1.1 to 4.1.3 Fixed In: 3.4.13, 3.6.7, 4.0.3, 4.2rc1 Description: Tabular and graphical reports, as well as new charts have a debug mode which displays raw data as plain text. This text is not correctly escaped and a crafted URL could use this vulnerability to inject code leading to XSS. References: https://bugzilla.mozilla.org/show_bug.cgi?id=697699 CVE Number: CVE-2011-3657 Class: Unauthorized Account Creation Versions: 2.23.3 to 3.4.12, 3.5.1 to 3.6.6, 3.7.1 to 4.0.2, 4.1.1 to 4.1.3 Fixed In: 3.4.13, 3.6.7, 4.0.3, 4.2rc1 Description: The User.offer_account_by_email WebService method ignores the user_can_create_account setting of the authentication method and generates an email with a token in it which the user can use to create an account. Depending on the authentication method being active, this could allow the user to log in using this account. Installations where the createemailregexp parameter is empty are not vulnerable to this issue. References: https://bugzilla.mozilla.org/show_bug.cgi?id=711714 CVE Number: CVE-2011-3667 Class: Cross-Site Request Forgery Versions: 2.0 to 3.4.12, 3.5.1 to 3.6.6, 3.7.1 to 4.0.2, 4.1.1 to 4.1.3 Fixed In: 4.2rc1 Description: The creation of bug reports and of attachments is not protected by a token and so they can be created without the consent of a user if the relevant code is embedded in an HTML page and the user visits this page. This behavior was intentional to let third-party applications submit new bug reports and attachments easily. But as this behavior can be abused by a malicious user, it has been decided to block submissions with no valid token starting from version 4.2rc1. Older branches are not patched to not break these third-party applications after the upgrade. References: https://bugzilla.mozilla.org/show_bug.cgi?id=703975 https://bugzilla.mozilla.org/show_bug.cgi?id=703983 CVE Number: none Vulnerability Solutions ======================= The fixes for these issues are included in the 3.4.13, 3.6.7, 4.0.3, and 4.2rc1 releases. Upgrading to a release with the relevant fixes will protect your installation from possible exploits of these issues. If you are unable to upgrade but would like to patch just the individual security vulnerabilities, there are patches available for each issue at the "References" URL for each vulnerability. Full release downloads, patches to upgrade Bugzilla from previous versions, and CVS/bzr upgrade instructions are available at: http://www.bugzilla.org/download/ Credits ======= The Bugzilla team wish to thank the following people/organizations for their assistance in locating, advising us of, and assisting us to fix this issue: Byron Jones Fr?d?ric Buclin Gervase Markham David Lawrence RedTeam Pentesting Reed Loden Max Kanat-Alexander Mario Gomes 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 mozilla.support.bugzilla newsgroup or the support-bugzilla mailing list. http://www.bugzilla.org/support/ has directions for accessing these forums. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJO/JlIAAoJEJZXZhv5X1hqXgQQAKkDxzJ2aJWXlKzmkv4re4FC lfKpVkJxAtWhr6uYIc8gpJ6rjAeV4VZY4GRKOy3Q5sFCsjUZwy3JotLzvIJg1vhe DU7SnUoH6arGmlsT9S2yC8fu9QJhpdgVpOCjXCOGLCGcQBcmq0WutTcfs/Cb/pWx 9i85bif9ihX7aTANRAGRHA2Hv6Hs4YAOJg07CtgS8hsaCmgDyEzuu21tpxsivoLw h7q6SbLQ7pfVQHjlXxyVP04OPh752nTfZWSPOXvuyhrcrb5oE4omJPNhucGeFTrG dtRxJiXgo0RUPENIUK7iGAIfNe8oUSqrI7UgA3FgabWpmyoEAOYL7CJAyPmZmC2Z RMDUX4Jbq67vlmSgc+iD3IHZmihBfPqtYSsW1C3ndhpfCLUTRLSWcHnZpAOw7HMi SgwufAKyK3DrqPwECmx3m0/M1JVVxJV/aY/ixJlduKklTcumevCESHXX5EkuFGqw P5dMYwmcQtp3iwN2bFSyAtURWJIvPmXRnJ4RlweAW6olQfx21sHJ46JTpHra4aCj BI4SFO3N8hfxPoyTfn7CtrDH/J9TSpEwm+hVDkX8uIPnaIWFGQ80q0WKRX7mr7gx 5pyS8xl4o0WWcpDpHPoPSjuYlU6GOZYBVrX642Qp5gum3A4XSIRojIHvTL19wHRm bqxjKTIcy+Wbh5rEf95s =vJYG -----END PGP SIGNATURE----- From dkl at mozilla.com Thu Dec 29 17:20:36 2011 From: dkl at mozilla.com (David Lawrence) Date: Thu, 29 Dec 2011 12:20:36 -0500 Subject: [ANN] Release of Bugzilla 4.2rc1, 4.0.3, 3.6.7, and 3.4.13 Message-ID: <4EFCA164.2070908@mozilla.com> Today we are announcing the first Release Candidate for Bugzilla 4.2, in addition to one new stable release and two security-only updates for the 3.4.x and 3.6.x series. Bugzilla 4.2rc1 is our first Release Candidate for Bugzilla 4.2. This release has received QA testing, and should be considerably more stable than the development releases before it. It is still not considered fully stable, and so you should understand that if you use it, you use it at your own risk. In particular, certain aspects of the WebServices have not yet been tested as part of this Release Candidate, so they may change before the final release. If feedback from this release candidate indicates that it is mostly stable, then Bugzilla 4.2 will be released in a few weeks. If feedback indicates that more extensive fixes are needed, there may be another release candidate after this one. Bugzilla 4.0.3 is our latest stable release. It contains various useful bug fixes and security improvements for the 4.0 branch. Bugzilla 3.6.7 and 3.4.13 are security updates for the 3.6 branch and the 3.4 branch, respectively. Download -------- Bugzilla is available at: http://www.bugzilla.org/download/ Security Advisory ----------------- There is a security advisory describing the security issues fixed in these releases, at: http://www.bugzilla.org/security/3.4.12/ Release Notes & Changes ----------------------- Before installing or upgrading, you should read the Release Notes for this version of Bugzilla: 4.2rc1: http://www.bugzilla.org/releases/4.2/release-notes.html 4.0.3: http://www.bugzilla.org/releases/4.0.3/release-notes.html 3.6.7: http://www.bugzilla.org/releases/3.6.7/release-notes.html 3.4.13: http://www.bugzilla.org/releases/3.4.13/release-notes.html It is VERY IMPORTANT to read the Release Notes if you are upgrading from one major version to another (like 3.4.x to 3.6.x). To see a list of all changes between your version of Bugzilla and the current version of Bugzilla, you can use the chart at: http://www.bugzilla.org/status/changes.html The Bugzilla Update ------------------- You can see the latest updates from the Bugzilla Project and the status of Bugzilla development on The Bugzilla Update: http://bugzillaupdate.wordpress.com/ Also, you can follow the Bugzilla Project on Twitter for frequent updates on new features being developed in Bugzilla, our current release plans, and much more: http://twitter.com/#!/bugzilla Report Bugs ----------- If you find a bug in Bugzilla, please report it! Instructions are at this URL: http://www.bugzilla.org/developers/reporting_bugs.html Support ------- You can ask questions for free on the mailing lists (or in IRC) about Bugzilla, or you can hire a paid consultant to help you out: Free Support: http://www.bugzilla.org/support/ Paid Support: http://www.bugzilla.org/support/consulting.html About Bugzilla -------------- Bugzilla is a "Defect Tracking System" or "Bug-Tracking System." Defect Tracking Systems allow individuals or groups of developers to keep track of outstanding bugs in their product effectively. Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being "free", Bugzilla has many features its expensive counterparts lack. Consequently, Bugzilla has quickly become a favorite of thousands of organizations across the globe, and is widely regarded as one of the top defect-tracking systems available. See http://www.bugzilla.org/about/ for more details. -- David Lawrence dkl at mozilla.com