Attacks/Breaches

9/28/2018
02:06 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
100%
0%

Facebook Hacked, 50 Million Users Affected

A vulnerability in Facebook's "View As" feature let attackers steal security tokens linked to 50 million accounts, the company confirms.

Facebook today confirmed a major security breach affecting nearly 50 million people, whose accounts were compromised when a vulnerability let hackers steal security tokens linked to their profiles.

The flaw was in Facebook's "View As" feature, which lets account holders see what their profile looks like to someone else – a friend, the public, etc. Attackers could exploit the bug to steal Facebook access tokens, which can be used to take over accounts. Tokens act as "digital keys" to keep people logged in so they don't have to enter a password every time they use the app.

Facebook has fixed the vulnerability, alerted law enforcement to the breach, and temporarily disabled the "View As" feature while it investigates the problem.

While the investigation is still ongoing, Facebook has confirmed the attack stemmed from a change it made to a video uploading feature in July 2017, which affected the "View As" feature. Attackers needed to find the bug, use it to steal an access token, then pivot from their target account to other accounts in order to steal more of these tokens.

There is no need for anyone to change their passwords, says Guy Rosen, VP of product management, in a blog post on the disclosure. Facebook has also reset the security tokens for the 50 million affected accounts, as well as 40 million additional accounts which have been viewed using the "View As" feature within the past year.

In total, about 90 million of Facebook's two billion users will have to log back into their accounts today, as well as any apps accessed via Facebook Login. When they do, they'll see a notification at the top of their News Feed explaining what happened.

Rosen states if Facebook discovers more affected accounts, it will immediately reset access tokens. For anyone taking the precautionary step of logging out of Facebook, the site's Security and Login section lets you see where you're logged in and lets you log out of all devices at once.

Facebook, still early in its analysis, says it does not know who might be behind this attack or where the actor(s) could be based. Today's news has left some industry experts concerned about why the vulnerability wasn't detected sooner.

"It's surprising to me that as popular as Facebook is, no white hat hacker ever discovered and reported this flaw in the past, neither an external pen tester nor Facebook's internal IT security team," says Paul Bischoff, privacy advocate with Comparitech. "I would be interested to know how long this flaw existed before it was discovered and exploited."

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 Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/5/2018 | 3:15:23 PM
Re: OMG What bout Insta
If Incrediboy's account was hacked - Zuckerberg - it would almost be worth it. 
colad1930
50%
50%
colad1930,
User Rank: Strategist
9/28/2018 | 10:12:09 PM
OMG What bout Insta
I have stopped using FB and I am addicted to their Ista. But I am now also worried about Insta security. Is Insta also vulnerable?
Microsoft, Mastercard Aim to Change Identity Management
Kelly Sheridan, Staff Editor, Dark Reading,  12/3/2018
Windows 10 Security Questions Prove Easy for Attackers to Exploit
Kelly Sheridan, Staff Editor, Dark Reading,  12/5/2018
Starwood Breach Reaction Focuses on 4-Year Dwell
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/5/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: I guess this answers the question: who's watching the watchers?
Current Issue
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19653
PUBLISHED: 2018-12-09
HashiCorp Consul 0.5.1 through 1.4.0 can use cleartext agent-to-agent RPC communication because the verify_outgoing setting is improperly documented. NOTE: the vendor has provided reconfiguration steps that do not require a software upgrade.
CVE-2018-19982
PUBLISHED: 2018-12-09
An issue was discovered on KT MC01507L Z-Wave S0 devices. It occurs because HPKP is not implemented. The communication architecture is APP > Server > Controller (HUB) > Node (products which are controlled by HUB). The prerequisite is that the attacker is on the same network as the target HU...
CVE-2018-19983
PUBLISHED: 2018-12-09
An issue was discovered on Sigma Design Z-Wave S0 through S2 devices. An attacker first prepares a Z-Wave frame-transmission program (e.g., Z-Wave PC Controller, OpenZWave, CC1110, etc.). Next, the attacker conducts a DoS attack against the Z-Wave S0 Security version product by continuously sending ...
CVE-2018-19980
PUBLISHED: 2018-12-08
Anker Nebula Capsule Pro NBUI_M1_V2.1.9 devices allow attackers to cause a denial of service (reboot of the underlying Android 7.1.2 operating system) via a crafted application that sends data to WifiService.
CVE-2018-19961
PUBLISHED: 2018-12-08
An issue was discovered in Xen through 4.11.x on AMD x86 platforms, possibly allowing guest OS users to gain host OS privileges because TLB flushes do not always occur after IOMMU mapping changes.