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 Executive Editor at DarkReading.com. 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
Crowdsourced vs. Traditional Pen Testing
Alex Haynes, Chief Information Security Officer, CDL,  3/19/2019
BEC Scammer Pleads Guilty
Dark Reading Staff 3/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
The State of Cyber Security Incident Response
The State of Cyber Security Incident Response
Organizations are responding to new threats with new processes for detecting and mitigating them. Here's a look at how the discipline of incident response is evolving.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7715
PUBLISHED: 2019-03-26
An issue was discovered in the Interpeak IPCOMShell TELNET server on Green Hills INTEGRITY RTOS 5.0.4. The main shell handler function uses the value of the environment variable ipcom.shell.greeting as the first argument to printf(). Setting this variable using the sysvar command results in a user-c...
CVE-2019-8981
PUBLISHED: 2019-03-26
tls1.c in Cameron Hamilton-Rich axTLS before 2.1.5 has a Buffer Overflow via a crafted sequence of TLS packets because the need_bytes value is mismanaged.
CVE-2019-10061
PUBLISHED: 2019-03-26
utils/find-opencv.js in node-opencv (aka OpenCV bindings for Node.js) prior to 6.1.0 is vulnerable to Command Injection. It does not validate user input allowing attackers to execute arbitrary commands.
CVE-2019-7711
PUBLISHED: 2019-03-26
An issue was discovered in the Interpeak IPCOMShell TELNET server on Green Hills INTEGRITY RTOS 5.0.4. The undocumented shell command "prompt" sets the (user controlled) shell's prompt value, which is used as a format string input to printf, resulting in an information leak of memory addre...
CVE-2019-7712
PUBLISHED: 2019-03-26
An issue was discovered in handler_ipcom_shell_pwd in the Interpeak IPCOMShell TELNET server on Green Hills INTEGRITY RTOS 5.0.4. When using the pwd command, the current working directory path is used as the first argument to printf() without a proper check. An attacker may thus forge a path contain...