Firefox vulnerability in its master password system has gone unpatched — for nine years!

Firefox tends to be one of the more secure browsers available to the general population. The browser is not without its flaws, but these flaws have tended to be fixed in a relatively timely fashion. But new reports indicate this is not always the case. According to a post released on Ad-Block Plus creator Wladimir Palant’s blog, there is a serious Firefox vulnerability that has gone unpatched for a mind-boggling nine years.

This Firefox vulnerability is related to the master password available for encryption of stored passwords. As Palant notes in his post, the actual encryption behind the master password is incredibly weak and easy to brute-force. The Firefox (and Thunderbird) master password system utilizes SHA-1 encryption, which is incredibly problematic. Palant states these issues as follows:

GPUs are extremely good at calculating SHA-1 hashes... a single Nvidia GTX 1080 graphics card can calculate 8.5 billion SHA-1 hashes per second. That means testing 8.5 billion password guesses per second. And humans are remarkably bad at choosing strong passwords... the average password is merely 40 bits strong. In order to guess a 40 bit password you will need to test 239 guesses on average. If you do the math, cracking a password will take merely a minute on average then."

Making the problem even worse for Mozilla is the fact that one of its own researchers uncovered the flaws in their master password system roughly nine years ago. This bug report states that “softtoken’s master password KDF process should be stronger (currently easily brute forced due to low iteration count),” and at the time (and for nearly a decade) Mozilla chose inaction with regards to this issue.

After numerous InfoSec news sites reported Wladimir Palant’s findings, Mozilla stated that they had a fix for the rather glaring issue. According to Bleeping Computer’s report by Catalin Cimpanu, “Mozilla finally provided an official answer, suggesting this would be fixed with the launch of Firefox’s new password manager component — currently codenamed Lockbox and available as an extension.”

I’m thoroughly disappointed in Mozilla for its lack of oversight on an issue that had long ago been reported by their researchers. Hopefully, they have learned from this humiliation and will be more diligent in the future.

Photo credit: Mozilla Foundation

Derek Kortepeter

Derek Kortepeter is a graduate of UCLA and tech journalist that is committed to creating an informed society with regards to Information Security. Kortepeter specializes in areas such as penetration testing, cryptography, cyber warfare, and governmental InfoSec policy.

Share
Published by
Derek Kortepeter

Recent Posts

IFA 2019: All the top smartphone announcements and unveilings

IFA 2019, this year’s version of the annual consumer electronics trade show, did not disappoint. Is one of these smartphones…

1 hour ago

Outlook connectivity: Troubleshooting and solving common issues

IT professionals all dread getting this fevered message from employees and clients: “I’m having Outlook connectivity issues!” Here’s what you…

6 hours ago

Using tags with Azure runbook automation to control your costs

Here’s a script designed to start and stop virtual machines based on tags associated at the resource group level. It…

9 hours ago

Software-defined perimeter solutions: Why this is the future of security

Traditional VPNs are showing their age in the modern cloud-powered workplace. That’s why software-defined perimeter solutions are in your future.

3 days ago

Why you need to check your virtualization host’s NUMA configuration

Should you disallow NUMA spanning in your Hyper-V architecture? There are two sides to this story, and you’ll get both…

3 days ago

Getting started with Visual Studio Code and integrating with Azure DevOps

Coding may not be the No. 1 job duty for cloud admins, but it is often a part of the…

3 days ago