Bugzilla 2.23.3 through 2.22.7, 3.0.x through 3.3.x, 3.4.x before 3.4.12, 3.5.x, 3.6.x before 3.6.6, 3.7.x, 4.0.x before 4.0.2, and 4.1.x before 4.1.3 allows remote attackers to determine the existence of private group names via a crafted parameter during (1) bug creation or (2) bug editing.

The remote host is affected by the vulnerability described in GLSA-201110-03 (Bugzilla: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Bugzilla. Please review       the CVE identifiers referenced below for details.
  Impact :

    A remote attacker could conduct cross-site scripting attacks, conduct       script insertion and spoofing attacks, hijack the authentication of       arbitrary users, inject arbitrary HTTP headers, obtain access to       arbitrary accounts, disclose the existence of confidential groups and its       names, or inject arbitrary e-mail headers.
    A local attacker could disclose the contents of temporarfy files for       uploaded attachments.
  Workaround :

    There is no known workaround at this time.

Several vulnerabilities were discovered in Bugzilla, a web-based bug tracking system.

  - CVE-2010-4572     By inserting particular strings into certain URLs, it     was possible to inject both headers and content to any     browser.

  - CVE-2010-4567, CVE-2011-0048     Bugzilla has a 'URL' field that can contain several     types of URL, including 'javascript:' and 'data:' URLs.
    However, it does not make 'javascript:' and 'data:' URLs     into clickable links, to protect against cross-site     scripting attacks or other attacks. It was possible to     bypass this protection by adding spaces into the URL in     places that Bugzilla did not expect them. Also,     'javascript:' and'data:' links were always shown as     clickable to logged-out users.

  - CVE-2010-4568     It was possible for a user to gain unauthorized access     to any Bugzilla account in a very short amount of time     (short enough that the attack is highly effective).

  - CVE-2011-0046     Various pages were vulnerable to Cross-Site Request     Forgery attacks. Most of these issues are not as serious     as previous CSRF vulnerabilities.

  - CVE-2011-2978     When a user changes his email address, Bugzilla trusts a     user-modifiable field for obtaining the current e-mail     address to send a confirmation message to. If an     attacker has access to the session of another user (for     example, if that user left their browser window open in     a public place), the attacker could alter this field to     cause the email-change notification to go to their own     address. This means that the user would not be notified     that his account had its email address changed by the     attacker.

  - CVE-2011-2381     For flagmails only, attachment descriptions with a     newline in them could lead to the injection of crafted     headers in email notifications when an attachment flag     is edited.

  - CVE-2011-2379     Bugzilla uses an alternate host for attachments when     viewing them in raw format to prevent cross-site     scripting attacks. This alternate host is now also used     when viewing patches in 'Raw Unified' mode because     Internet Explorer 8 and older, and Safari before 5.0.6     do content sniffing, which could lead to the execution     of malicious code.

  - CVE-2011-2380, CVE-2011-2979     Normally, a group name is confidential and is only     visible to members of the group, and to non-members if     the group is used in bugs. By crafting the URL when     creating or editing a bug, it was possible to guess if a     group existed or not, even for groups which weren't used     in bugs and so which were supposed to remain     confidential.

A Bugzilla Security Advisory reports :

The following security issues have been discovered in Bugzilla :

- Internet Explorer 8 and older, and Safari before 5.0.6 do content sniffing when viewing a patch in 'Raw Unified' mode, which could trigger a cross-site scripting attack due to the execution of malicious code in the attachment.

- It is possible to determine whether or not certain group names exist while creating or updating bugs.

- Attachment descriptions with a newline in them could lead to the injection of crafted headers in email notifications sent to the requestee or the requester when editing an attachment flag.

- If an attacker has access to a user's session, he can modify that user's email address without that user being notified of the change.

- Temporary files for uploaded attachments are not deleted on Windows, which could let a user with local access to the server read them.

- Up to Bugzilla 3.4.11, if a BUGLIST cookie is compromised, it can be used to inject HTML code when viewing a bug report, leading to a cross-site scripting attack.

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

ID	Name	Product	Family	Severity
56445	GLSA-201110-03 : Bugzilla: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
56444	Debian DSA-2322-1 : bugzilla - several vulnerabilities	Nessus	Debian Local Security Checks	high
55847	FreeBSD : bugzilla -- multiple vulnerabilities (dc8741b9-c5d5-11e0-8a8e-00151735203a)	Nessus	FreeBSD Local Security Checks	medium

Detections

Analytics

CVE-2011-2380

medium

Tenable Plugins

high

high

medium