From dkl at mozilla.com Tue Jan 31 23:39:31 2012 From: dkl at mozilla.com (David Lawrence) Date: Tue, 31 Jan 2012 18:39:31 -0500 Subject: [ANN] Release of Bugzilla 4.2rc2, 4.0.4, 3.6.8, and 3.4.14 Message-ID: <4F287BB3.40104@mozilla.com> Today we are announcing the second 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.2rc2 is our second 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. This will most likely be the last release candidate before 4.2 final. Bugzilla 4.0.4 is our latest stable release. It contains various useful bug fixes and security improvements for the 4.0 branch. Bugzilla 3.6.8 and 3.4.14 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.13/ Release Notes & Changes ----------------------- Before installing or upgrading, you should read the Release Notes for this version of Bugzilla: 4.2rc2: http://www.bugzilla.org/releases/4.2/release-notes.html 4.0.4: http://www.bugzilla.org/releases/4.0.4/release-notes.html 3.6.8: http://www.bugzilla.org/releases/3.6.8/release-notes.html 3.4.14: http://www.bugzilla.org/releases/3.4.14/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 Release Manager, Bugzilla Project From lpsolit at gmail.com Tue Jan 31 23:40:54 2012 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Wed, 01 Feb 2012 00:40:54 +0100 Subject: Security advisory for Bugzilla 4.2rc2, 4.0.4, 3.6.8 and 3.4.14 Message-ID: <4F287C06.8050800@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 a user creates a new account, Bugzilla doesn't correctly reject email addresses containing non-ASCII characters, which could be used to impersonate another user account. * A CSRF vulnerability in the implementation of the JSON-RPC API could be used to make changes to bugs or execute some admin tasks without the victim's knowledge. All affected installations are encouraged to upgrade as soon as possible. Vulnerability Details ===================== Class: Account Impersonation Versions: 2.0 to 3.4.13, 3.5.1 to 3.6.7, 3.7.1 to 4.0.3, 4.1.1 to 4.2rc1 Fixed In: 3.4.14, 3.6.8, 4.0.4, 4.2rc2 Description: When a user creates a new account, Bugzilla doesn't correctly reject email addresses containing non-ASCII characters, which could be used to impersonate another user account. Such email addresses could look visually identical to other valid email addresses, and an attacker could try to confuse other users and be added to bugs he shouldn't have access to. References: https://bugzilla.mozilla.org/show_bug.cgi?id=714472 CVE Number: CVE-2012-0448 Class: Cross-Site Request Forgery Versions: 3.5.1 to 3.6.7, 3.7.1 to 4.0.3, 4.1.1 to 4.2rc1 Fixed In: 3.6.8, 4.0.4, 4.2rc2 Description: Due to a lack of validation of the Content-Type header when making POST requests to jsonrpc.cgi, a possible CSRF vulnerability was discovered. If a user visits an HTML page with some malicious JS code in it, an attacker could make changes to a remote Bugzilla installation on behalf of the victim's account by using the JSON-RPC API. The user would have had to be already logged in to the target site for the vulnerability to work. References: https://bugzilla.mozilla.org/show_bug.cgi?id=718319 CVE Number: CVE-2012-0440 Vulnerability Solutions ======================= The fixes for these issues are included in the 3.4.14, 3.6.8, 4.0.4, and 4.2rc2 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: Fr?d?ric Buclin Max Kanat-Alexander Byron Jones Mario Gomes James Kettle 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/ iQIcBAEBAgAGBQJPKHwFAAoJEJZXZhv5X1hqtVAP/ifrYpIgwGHZpMd+Ql7kY9CU GmcgGrwpvA3OWvXUOMkM/M1oLzgqv8IXMyD/Y+RcEGI3GkQ+xsoEePvHMa2b6vCY t2Se3lsN32+ggxYQypp8e4Eg+nvZth+q2vb1ueFZuoKEkquDKTvMOFO4DTZfMNbZ Dek3TFfF1bAw76Uf0sPsb730D477WVROLcWa2ZFz7PNAqX93AjsJg+Ii8C3q1K3g o23Xih8JmRXz/FuLAL3HnQQJALdFKbNuX5jsBejn5XITFo8gx/AAWY1qBgqptz6J FTKij0XLhqcY3dsWGnqpqYWbQyhIlUPiyNQ4Ot4XDLEzKD82ve8uVFhH4f7siQAP pAxIxrOo/WI8foSeLpIwO92vXwsqtSXc+YKsNz8l8htkOdzR9O1DNeJr/nRCf73v ov7k/lVUEQ3MzATGoCSgb6Sf211rY8wpdnpOEF8C361AGDDKL01qQx/abDZEgI77 i9gHEX48n/j6ke+yivggZy19h5RfDDVB9kFsrbWurjr6sGxblQmPw/0A948/4XmX HQUjHsmKBGzVuhAkGEO4aTebKlDpGM71Ikbi+YL9+/W3vhb1AMPxZOWRzUWjDHNH gsvduK/gvP80EJqGSSPuxqhaNalnAFi7E1ZSLpGzIlv6/r2aJYlqebP0MeUnkEVW vtINhZlaMY0gEiU/YB+1 =Szn1 -----END PGP SIGNATURE-----