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.

Cloud

10/12/2018
04:35 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Facebook Update: 30 Million Users Actually Hit in its Recent Breach

The good news: That number is less than the original estimate of 50 million. The bad news: It might not have been the only attack.

Facebook today confirmed the actual number of users hit in its recent data breach is 30 million rather than its original estimate of 50 million. 

The social media giant also is investigating other possible "smaller-scale attacks" leveraging the vulnerability in its code that was exploited in the breach, which it first reported late last month. The attackers already had control of a set of user accounts that were then connected to those users' Facebook friends.

"They used an automated technique to move from account to account so they could steal the access tokens of those friends, and for friends of those friends, and so on, totaling about 400,000 people," said Guy Rosen, vice president of product management for Facebook, in a post today.

This allowed the attackers to obtain Facebook profiles and see their timeline posts, lists of friends, groups, and names in recent Messenger chats. "Message content was not available to the attackers, with one exception. If a person in this group was a Page admin whose Page had received a message from someone on Facebook, the content of that message was available to the attackers," according to Facebook.

The FBI, which is investigating the attack, has asked the social media giant not to discuss who may be behind it.

Here's how the attack spread: The attackers used part of the 400,000 users' friends lists to steal tokens of 30 million people on Facebook. Some 15 million Facebook users' names, phone numbers, and email addresses were pilfered. For another 14 million users, their usernames and profile details – such as gender, relationship status, hometown, birthdate, city, and devices – as well as their 15 most recent searches from the platform also were stolen. That's in addition to their names, phone numbers, and email addresses.

The remaining 1 million Facebook members' information was not accessed in the attack.

'View As' Bug
Facebook last week announced that a previously unknown vulnerability in its code that existed between July 2017 and September 2018 had been exploited by attackers to steal Facebook access tokens, which could be used to hijack user accounts. Tokens are basically digital keys that allow users to remain logged into the social media platform without constantly signing in.

"The vulnerability was the result of a complex interaction of three distinct software bugs and it impacted "View As," a feature that lets people see what their own profiles look like to someone else," Rosen said.

Facebook discovered the attack on Sept. 25, after noticing unusual activity starting on Sept. 14. "Within two days, we closed the vulnerability, stopped the attack, and secured people's accounts by restoring the access tokens for people who were potentially exposed. As a precaution, we also turned off 'View As,'" Rosen said.

The company suggests Facebook users check the Help Center. It has already begun sending messages to affected victims about what information was stolen and how to protect themselves.

Note from author: While writing this story, I received a notice from Facebook today that I'm one of the breach victims: My name, email address, and phone number were accessed by the attackers.  

Related Content:

 

Black Hat Europe returns to London Dec 3-6 2018  with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment:   It's a PEN test of our cloud security.
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5124
PUBLISHED: 2020-01-25
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13001.50005. A specially crafted pixel shader can cause a denial of service. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered fro...
CVE-2019-5146
PUBLISHED: 2020-01-25
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13025.10004. A specially crafted pixel shader can cause a denial of service. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered fro...
CVE-2019-5147
PUBLISHED: 2020-01-25
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13003.1007. A specially crafted pixel shader can cause a denial of service. An attacker can provide a specially crafted shader file to trigger this vulnerability. This vulnerability can be triggered from...
CVE-2019-5183
PUBLISHED: 2020-01-25
An exploitable type confusion vulnerability exists in AMD ATIDXX64.DLL driver, versions 26.20.13031.10003, 26.20.13031.15006 and 26.20.13031.18002. A specially crafted pixel shader can cause a type confusion issue, leading to potential code execution. An attacker can provide a specially crafted shad...
CVE-2020-5226
PUBLISHED: 2020-01-24
Cross-site scripting in SimpleSAMLphp before version 1.18.4. The www/erroreport.php script allows error reports to be submitted and sent to the system administrator. Starting with SimpleSAMLphp 1.18.0, a new SimpleSAML\Utils\EMail class was introduced to handle sending emails, implemented as a wrapp...