Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

05:55 PM
Connect Directly

Facebook Announces Formal Vulnerability Disclosure Policy for Third-Party Bugs

The social media giant has also launched a new website for sharing information on WhatsApp security.

Facebook today rolled out a formal policy for disclosing vulnerabilities in third-party products and also announced the creation of a new website for providing security updates and bug disclosures related to WhatsApp.

Facebook's new Security Vulnerability Disclosure Policy formally codifies a set of practices the social media behemoth said it would follow in releasing information about any security issues its researchers might uncover in third-party products.

Related Content:

Thousands of Facebook Users Hit in Malware Distribution Campaign

Facebook Patches Critical WhatsApp Security Flaw

The Threat from the Internet—and What Your Organization Can Do About It

Under the policy, when Facebook informs a third party about a bug, it will give that entity 21 days to let Facebook know how the issue will be mitigated. If the third party does not respond, Facebook says it reserves the right to disclose the bug publicly. The company says it will do the same thing if no fix is available after 90 days. Facebook's new policy disclosure page lists several other processes and steps it will take to ensure the third party has every opportunity to understand and fix a bug before the disclosure clock runs down.

Facebook has already been informally following many of the practices. The goal in announcing a structured policy is to "unambiguously explain" expectations, timelines, and reporting processes when security issues are discovered in third-party code and systems, Facebook said Thursday.

"From time to time, in the course of our work we come across security vulnerabilities in third-party code, including open source, closed source vendor software, or devices among other things," says Nathaniel Gleicher, head of security policy at Facebook.

In the past, Facebook researchers have found and reported multiple vulnerabilities in VPN clients, VPN servers, optical switches, virtualization software, file storage appliances, and email clients, among other types of software or devices, Gleicher says.

"This policy codifies core principles we have always strived to follow: Put users first, minimize harm, and share our findings to help the infosec community to patch issues quickly," he says.

In recent years the security industry has worked on building consensus around responsible bug disclosure practices. Though a majority of disclosures these days adhere to broadly used policies such as the one Facebook announced today, there have been instances where security researchers and vendors have released bug details before a fix for it was available.

One notable example involved a bug in a Windows crypto library that a researcher from Google's Project Zero program disclosed in June 2019 even as a fix for it was getting ready. In that case, the researcher described the disclosure as happening only after he had provided Microsoft with adequate time for fixing the issue. Google, like other tech companies, has a formally articulated bug disclosure policy that has a similar timeline as Facebook's policy,

Facebook and hundreds of other companies have tried to mitigate the risk of zero-day disclosures involving their products by implementing formal bug-bounty programs that give independent and third-party security researchers a way to look for and responsibly report bugs in their products. Facebook has so far awarded over $9.8 million in bounties to researchers from some 60 countries for responsibly reporting vulnerabilities in Facebook products and services. In 2019 alone, the company paid over $2.2 million to such independent researchers, Gleicher says.

In addition to the new disclosure policy, Facebook also has launched a new website that will regularly provide information on WhatsApp security — including newly patched bugs. According to Facebook, some one-third of the bugs reported in WhatsApp come in via its bug-bounty program, and like most bugs they are patched the same day.

"WhatsApp has disclosed CVEs via MITRE previously and we'll continue to do so," Gleicher notes. "But we also wanted to make it easy for security researchers and people using our service to have updates about and understand the security work [around WhatsApp]. We hope that anyone who views the page will get a better understanding of the security of WhatsApp."


Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Overcoming the Challenge of Shorter Certificate Lifespans
Mike Cooper, Founder & CEO of Revocent,  10/15/2020
US Counterintelligence Director & Fmr. Europol Leader Talk Election Security
Kelly Sheridan, Staff Editor, Dark Reading,  10/16/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-10-21
Prior to 0.10.0-beta, LND (Lightning Network Daemon) would have accepted a counterparty high-S signature and broadcast tx-relay invalid local commitment/HTLC transactions. This can be exploited by any peer with an open channel regardless of the victim situation (e.g., routing node, payment-receiver,...
PUBLISHED: 2020-10-21
Prior to 0.11.0-beta, LND (Lightning Network Daemon) had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn't verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount collis...
PUBLISHED: 2020-10-20
Cross-site request forgery in Nagios XI 5.7.3 allows a remote attacker to perform sensitive application actions by tricking legitimate users into clicking a crafted link.
PUBLISHED: 2020-10-20
Improper neutralization of special elements used in an OS command in Nagios XI 5.7.3 allows a remote, authenticated admin user to execute operating system commands with the privileges of the apache user.
PUBLISHED: 2020-10-20
Improper neutralization of argument delimiters in a command in Nagios XI 5.7.3 allows a remote, authenticated admin user to write to arbitrary files and ultimately execute code with the privileges of the apache user.