At Mozilla, we believe in an open web that is safe to use. To that end, we improve and maintain the security of people using Firefox around the world. This includes a solid track record of responding to security bugs in the wild, especially with bug bounty programs such as Pwn2Own. As soon as we discover a critical security issue in Firefox, we plan and ship a rapid fix. This post describes how we recently fixed an exploit discovered at Pwn2Own in less than 21 hours, a success only made possible through the collaborative and well-coordinated efforts of a global cross-functional team of release and QA engineers, security experts, and other stakeholders.<\/p>\n
Pwn2Own<\/a> is an annual computer hacking contest where participants aim to find security vulnerabilities in major software such as browsers. Two weeks ago, this event took place in Vancouver, Canada, where participants investigated everything from Chrome, Firefox, and Safari to MS Word and even the code currently running on your car<\/a>. Without getting into the technical details<\/a> of the exploit here, this blog post will describe how Mozilla quickly responds to and ships updated builds for exploits found during Pwn2Own.<\/p>\n To give you a sense of scale, Firefox is a massive piece of software: 30 million+ lines of code, six platforms (Windows 32 & 64bit, GNU\/Linux 32 & 64bit, Mac OS X and Android), 90 languages, plus installers, updaters, etc. Releasing such a beast involves coordination across many cross-functional teams spanning the entire globe.<\/p>\n The timing of the Pwn2Own event is known weeks beforehand, so Mozilla is always ready when it rolls around! The Firefox train release calendar<\/a> takes into consideration the timing of Pwn2Own. We try not to ship a new version of Firefox to end users on the release channel on the same day as Pwn2Own to hopefully avoid multiple updates close together. This also means that we are prepared to ship a patched version of Firefox as soon as we know what vulnerabilities were discovered if any at all.<\/p>\n The specific exploit disclosed at Pwn2Own consisted of two bugs<\/a>, a necessity when typical web content is rendered inside of a proverbial browser sandbox: These two sophisticated exploits<\/a> took an admirable amount of effort to reveal and leverage. Nevertheless, as soon as it was discovered, Mozilla engineers got to work, shipping a new release within 21 hours! We certainly weren\u2019t the only browser \u201cpwned\u201d, but we were the first of all, to patch our vulnerability<\/a>. That\u2019s right: before you knew about this exploit, we had already protected you from it.<\/p>\n As scary as this might sound, Sandbox Escapes, like many web browser exploits, are an issue common to all browsers, thanks to the evolving nature of the internet. Firefox developers are always eager to find and resolve these security issues as quickly as possible to ensure our users stay safe. We do this continuously by shipping new mitigations like win32k lockdown, site isolation, investing in security fuzzing<\/a>, and promoting bug bounties<\/a> for similar escapes. In the interest of openness and transparency, we also continuously invite and reward security researchers who share their newest attacks, which helps us keep our product safe even when there isn\u2019t a Pwn2Own to participate in.<\/p>\n If you\u2019re interested in learning more about Mozilla\u2019s security initiatives or Firefox security, here are some resources to help you get started:<\/p>\n Mozilla Security Furthermore, if you want to kickstart your own security research in Firefox, we invite you to follow our deeply technical blog at Attack & Defense \u2013 Firefox Security Internals for Engineers, Researchers, and Bounty Hunters<\/a> .<\/p>\n Past Pwn2Own Blog: https:\/\/hacks.mozilla.org\/2018\/03\/shipping-a-security-update-of-firefox-in-less-than-a-day\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"So What Happened?<\/b><\/h2>\n
Related Resources<\/b><\/h2>\n
\n<\/a>Mozilla Security Blog
\n<\/a>Bug Bounty Program
\n<\/a>Mozilla Security playlist on YouTube<\/a><\/p>\n