EUVD-2003-1033

Malware in sbrugna...

EUVD-2006-2421

Malware in sbrugna...

EUVD-2007-0789

Malware in sbrugna...

EUVD-2008-7245

Malware in sbrugna...

EUVD-2012-5760

Malware in sbrugna...

EUVD-2011-2947

Malware in sbrugna...

SUSE CVE-2011-2979

Bugzilla 4.1.x before 4.1.3 generates different responses for certain assignee queries depending on whether the group name is valid, which allows remote attackers to determine the existence of private group names via a custom search. NOTE: this vulnerability exists because of a CVE-2010-2756...

Bugzilla 'Install/Filesystem.pm' Information Disclosure Vulnerability

This host is running Bugzilla and is prone to information disclosure vulnerability. OpenVAS Vulnerability Test $Id: gbbugzillainfodiscvulnjul10.nasl 5263 2017-02-10 13:45:51Z teissa $ Bugzilla 'Install/Filesystem.pm' Information Disclosure Vulnerability Authors: Antu Sanadi Copyright: Copyright c...

CVE-2003-0012

The data collection script for Bugzilla 2.14.x before 2.14.5, 2.16.x before 2.16.2, and 2.17.x before 2.17.3 sets world-writable permissions for the data/mining directory when it runs, which allows local users to modify or delete the data...

CVE-2004-0702

DBI in Bugzilla 2.17.1 through 2.17.7 displays the database password in an error message when the SQL server is not running, which could allow remote attackers to gain sensitive information...

[BUGZILLA] Security Advisory - information leak

Bugzilla Security Advisory November 9, 2003 Summary ======= Bugzilla is a Web-based bug-tracking system, currently used by a large number of software projects. This advisory covers a security bug which was accidently introduced in development version 2.17.5 and subsequently fixed in the Bugzilla...

CVE-2001-1405

Bugzilla before 2.14 does not restrict access to sanitycheck.cgi, which allows local users to cause a denial of service CPU consumption via a flood of requests to sanitycheck.cgi...

CVE-2002-0008

Bugzilla before 2.14.1 allows remote attackers to 1 spoof a user comment via an HTTP request to processbug.cgi using the "who" parameter, instead of the Bugzillalogin cookie, or 2 post a bug as another user by modifying the reporter parameter to enterbug.cgi, which is passed to postbug.cgi...