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.

Operational Security

9/28/2018
02:30 PM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

50M Facebook Accounts Exposed Due to Software Vulnerability

A vulnerability in Facebook's 'View As' feature could have exposed the personal information of 50 million of the social network's users.

Facebook is facing yet another controversy over how the social media company protects and secures the personal data of its users.

On Friday, the company announced that a vulnerability in the platform's "View As" feature exposed the data of about 50 million Facebook users to attackers. This feature allows users to view their Facebook profile as someone else.

The vulnerability allowed the attackers to steal the access tokens of users and take over those accounts and profiles. These access tokens are the digital keys that allow users to keep their profiles open without having to re-login into the site.

(Source: Flickr)
(Source: Flickr)

In its September 28 announcement, Facebook's Guy Rosen, vice president of Product Management, wrote that the investigation remains in its early stages and that law enforcement has been notified about the breach.

Security researchers at Facebook first noticed the security flaw on Tuesday, Sept. 25 and a patch has already been applied.

Facebook has already reset the tokens of the 50 million users targeted in the attack. In addition, the company reset the tokens of an additional 40 million users, meaning that some 90 million users will not have to re-log back in when going to their Facebook page.

All told, Facebook has about 2.23 billion users worldwide.

Finally, Facebook is shutting down View As for the time being until the company's security review is complete. While it's not clear what happened yet, Rosen wrote that an update the company rolled out to its video uploading feature in July 2017 created the vulnerability in the platform.

"Since we've only just started our investigation, we have yet to determine whether these accounts were misused or any information accessed," Rosen wrote in a blog post. "We also don't know who's behind these attacks or where they're based. We're working hard to better understand these details -- and we will update this post when we have more information, or if the facts change. In addition, if we find more affected accounts, we will immediately reset their access tokens."

Chris Morales, the head of security analytics at Vectra, a San Jose-based provider of automated threat management tools, noted in an email that these types of vulnerabilities are common in software and that the more complex the platform, the more flaws there are. He added that Facebook did the right thing by alerting users as soon as possible.

"All code has these forms of flaw that allow unintended use of software, and the more complex the software gets the more likely these type of flaws exist," Morales wrote in an email to Security Now. "I do commend Facebook for identifying and responding to the compromise so quickly. It is unfortunate for users however, and it is also unfortunate for Facebook at a time when they under intense scrutiny along with the recent departure of Facebook's CSO, Alex Stamos."

Since the start of the year, Facebook has come under increasing scrutiny for how it secures and uses the vast trove of data it collects from its 2 billion users. Most recently, Facebook's COO Sheryl Sandberg appeared before a congressional committee to answer questions about election interference, how the company uses its data and how it moderates the online content users create.

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...