![]() What are the best practices around linking versions and bug tracking ? How do you keep track of these versions (found, planned and multiple fixed) in Bugzilla? This is where I need your collective wisdom : this can actually be multiple numbers where we did a retroactive fix for some of these customers (this happens VERY often). ![]() The version in which the bug was found (version), the version in which we plan to fix (milestone) the bug and the version in which it has ultimately been fixed (open to suggestions). Lastly, for various reasons, we want to track three different version information : The end result is that the version combo box is ludicrously long. To make matters worse, because of contractual limitations it is not always possible to upgrade the clients to the latest and greatest, so we must branch, fix, test and release, on the version they currently have, yielding yet another version number. Mix in the fact that our versioning management has been through a few iterations it generated a lot of different versions in the wild. We have a legacy application that has been around for a long time. In August, Mozilla revealed that the email addresses and encrypted passwords of 97,000 users who had created test installations on were inadvertently dumped on a public Web server.We are in the process of migrating our bug tracking to Bugzilla from a really old version of track and I am running out of Advil. This isn’t the only security incident affecting Bugzilla in the past months. OpenSSH, Red Hat, Wikimedia and Apache also announced patching their installations. On Monday, Bugzilla released a software update that addresses the unauthorized account creation issue, along with three other security vulnerabilities. However, Mozilla says there is no evidence that the vulnerability has been exploited by malicious actors. The vulnerability affects all Bugzilla versions after 2.23.3, which was released in 2006. Roughly 150 organizations and projects run public Bugzilla installations, including Mozilla, Gnome, KDE, the Apache Project, LibreOffice, Open Office, OpenSSH, the Linux Kernel and various Linux distributions. ![]() However, the Mozilla security group, which has access to unfixed vulnerabilities, is not affected by this issue because its members are added individually. ![]() For example, in the case of Mozilla, employees are added to a particular group based on their email addresses, but this only gives them access to certain bugs, such as the ones affecting human resources. The vulnerability can be dangerous on Bugzilla installations where users are added to a certain group based on their email address domain.īugzilla lead developer Gervase Markham clarified in a blog post that not all unfixed vulnerabilities reported through Bugzilla were exposed by the vulnerability. Rubin created a series of test accounts, such as and, to demonstrate his findings. This breaks the email validation process, and allows an attacker to create accounts which match the groups regex policies, effectively becoming a privileged user,” explained Netanel Rubin, the Check Point researcher who uncovered the vulnerability. “The successful exploitation of the vulnerability allows the manipulation of any DB field at the user creation procedure, including the ‘login_name’ field. In some cases, this could expose sensitive information on undisclosed flaws. The issue appears to be caused by a security flaw that’s specific to the Perl programming language.Īn attacker can exploit the vulnerability to create an account on the Bugzilla platform for an email address they don’t own. The vulnerability, which has been assigned CVE-2014-1572, was reported to Bugzilla on September 30 by researchers at Check Point Software Technologies. The development team behind the Bugzilla bug-tracking software has released an update that addresses several security issues, including a critical flaw that could lead to privilege escalation.
0 Comments
Leave a Reply. |