Multiple vulnerabilities have been found in Bugzilla, the worst of which could lead to the escalation of privileges.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/bugzilla | * | < 5.0.3 | >= 5.0.3, > 4.4.12 (revision) |
Bugzilla is the bug-tracking system from the Mozilla project.
Multiple vulnerabilities have been discovered in Bugzilla. Please review the CVE identifiers referenced below for details.
Privileged account holders could execute system level commands, and the new user process could be exploited to allow for the escalation of privileges.
There is no known workaround at this time.
All Bugzilla 4.x users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/bugzilla-4.4.12"
All Bugzilla 5.x users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/bugzilla-5.0.3"
Multiple vulnerabilities were found in Bugzilla, the worst of which leading to privilege escalation.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/bugzilla | * | < 3.6.6 | >= 3.6.6 |
Bugzilla is the bug-tracking system from the Mozilla project.
Multiple vulnerabilities have been discovered in Bugzilla. Please review the CVE identifiers referenced below for details.
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.
There is no known workaround at this time.
All Bugzilla users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/bugzilla-3.6.6"
NOTE: This is a legacy GLSA. Updates for all affected architectures are available since August 27, 2011. It is likely that your system is already no longer affected by this issue.
Bugzilla is prone to multiple medium severity vulnerabilities.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/bugzilla | * | < 3.2.6 | >= 3.2.6 |
Bugzilla is a bug tracking system from the Mozilla project.
Multiple vulnerabilities have been reported in Bugzilla. Please review the CVE identifiers referenced below for details.
A remote attacker might be able to disclose local files, bug information, passwords, and other data under certain circumstances. Furthermore, a remote attacker could conduct SQL injection, Cross-Site Scripting (XSS) or Cross-Site Request Forgery (CSRF) attacks via various vectors.
There is no known workaround at this time.
All Bugzilla users should upgrade to an unaffected version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/bugzilla-3.2.6"
Bugzilla 2.x and 3.0 have reached their end of life. There will be no more security updates. All Bugzilla 2.x and 3.0 users should update to a supported Bugzilla 3.x version.
Bugzilla contains several vulnerabilities, some of them possibly leading to the remote execution of arbitrary code.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/bugzilla | * | < 3.0.1 | >= 2.20.5 (revision), >= 2.22.3 (revision), >= 3.0.1, >= 2.22.5 (revision), >= 2.20.6 (revision) |
Bugzilla is a web application designed to help with managing software development.
Masahiro Yamada found that from the 2.17.1 version, Bugzilla does not properly sanitize the content of the "buildid" parameter when filing bugs (CVE-2007-4543). The next two vulnerabilities only affect Bugzilla 2.23.3 or later, hence the stable Gentoo Portage tree does not contain these two vulnerabilities: Loic Minier reported that the "Email::Send::Sendmail()" function does not properly sanitise "from" email information before sending it to the "-f" parameter of /usr/sbin/sendmail (CVE-2007-4538), and Frederic Buclin discovered that the XML-RPC interface does not correctly check permissions in the time-tracking fields (CVE-2007-4539).
A remote attacker could trigger the "buildid" vulnerability by sending a specially crafted form to Bugzilla, leading to a persistent XSS, thus allowing for theft of credentials. With Bugzilla 2.23.3 or later, an attacker could also execute arbitrary code with the permissions of the web server by injecting a specially crafted "from" email address and gain access to normally restricted time-tracking information through the XML-RPC service.
There is no known workaround at this time.
All Bugzilla users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose www-apps/bugzilla
Bugzilla is vulnerable to cross-site scripting, script injection, and request forgery.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/bugzilla | * | < 2.18.6 | >= 2.18.6 |
Bugzilla is a bug tracking system used to allow developers to more easily track outstanding bugs in products.
The vulnerabilities identified in Bugzilla are as follows:
An attacker could inject scripts into the content loaded by a user's browser in order to have those scripts executed in a user's browser in the context of the site currently being viewed. This could include gaining access to privileged session information for the site being viewed. Additionally, a user could forge an HTTP request in order to create, modify, or delete bugs within a Bugzilla instance. Lastly, an unauthorized user could view sensitive information about bugs or bug attachments.
There is no known workaround at this time.
All Bugzilla users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/bugzilla-2.18.6"
Multiple vulnerabilities in Bugzilla could allow remote users to modify bug flags or gain sensitive information.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-apps/bugzilla | * | < 2.18.3 | >= 2.18.3 |
Bugzilla is a web-based bug-tracking system used by many projects.
Bugzilla allows any user to modify the flags of any bug (CAN-2005-2173). Bugzilla inserts bugs into the database before marking them as private, in connection with MySQL replication this could lead to a race condition (CAN-2005-2174).
By manually changing the URL to process_bug.cgi, a remote attacker could modify the flags of any given bug, which could trigger an email including the bug summary to be sent to the attacker. The race condition when using Bugzilla with MySQL replication could lead to a short timespan (usually less than a second) where the summary of private bugs is exposed to all users.
There are no known workarounds at this time.
All Bugzilla users should upgrade to the latest available version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-apps/bugzilla-2.18.3"