From the Bugtraq mailing list today: 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
GLSA vote: no.
GLSA Vote: no too, closing noglsa.
CVE-2011-3669 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3669): Cross-site request forgery (CSRF) vulnerability in attachment.cgi in Bugzilla 2.x, 3.x, and 4.x before 4.2rc1 allows remote attackers to hijack the authentication of arbitrary users for requests that upload attachments. CVE-2011-3668 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3668): Cross-site request forgery (CSRF) vulnerability in post_bug.cgi in Bugzilla 2.x, 3.x, and 4.x before 4.2rc1 allows remote attackers to hijack the authentication of arbitrary users for requests that create bug reports. CVE-2011-3667 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3667): The User.offer_account_by_email WebService method in Bugzilla 2.x and 3.x before 3.4.13, 3.5.x and 3.6.x before 3.6.7, 3.7.x and 4.0.x before 4.0.3, and 4.1.x through 4.1.3, when createemailregexp is not empty, does not properly handle user_can_create_account settings, which allows remote attackers to create user accounts by leveraging a token contained in an e-mail message. CVE-2011-3657 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3657): Multiple cross-site scripting (XSS) vulnerabilities in Bugzilla 2.x and 3.x before 3.4.13, 3.5.x and 3.6.x before 3.6.7, 3.7.x and 4.0.x before 4.0.3, and 4.1.x through 4.1.3, when debug mode is used, allow remote attackers to inject arbitrary web script or HTML via vectors involving a (1) tabular report, (2) graphical report, or (3) new chart.
(In reply to comment #3) > CVE-2011-3669 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3669): > Cross-site request forgery (CSRF) vulnerability in attachment.cgi in > Bugzilla 2.x, 3.x, and 4.x before 4.2rc1 allows remote attackers to hijack > the authentication of arbitrary users for requests that upload attachments. > > CVE-2011-3668 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-3668): > Cross-site request forgery (CSRF) vulnerability in post_bug.cgi in Bugzilla > 2.x, 3.x, and 4.x before 4.2rc1 allows remote attackers to hijack the > authentication of arbitrary users for requests that create bug reports. > Looks like the CSRF issues were assigned these two issues after upstream released the advisories.
