Vulnerabilities / Threats

6/8/2018
11:35 AM

Facebook Bug Sets 14M Users' Settings to 'Public'

The default sharing setting was accidentally changed for millions of accounts during a four-day period last month.



If you haven't checked your Facebook privacy settings in a while, now would be a good time. The social media giant recently informed users of a bug that changed the default sharing setting from "private" to "public" for about 14 million people from May 18 through May 22, 2018.

Facebook was testing a new feature that led to the bug, which automatically suggested sharing publicly when people created new posts. The new feature focuses on how to highlight items on your profile; because these are public, the suggested audience for all new posts was also public.

Upon discovering the bug, Facebook reportedly went back and adjusted the privacy settings for all posts shared by affected people during the five-day window, according to CNN.

The 14 million people affected by the bug are being notified, Facebook reports. It also urges anyone alerted to review any posts they made during that time. The bug does not affect posts made before May 18, and people can still choose their audiences as usual.

This is the latest privacy-related fumble for Facebook, which recently suspended 200 apps after the Cambridge Analytica scandal exposed information belonging to millions. It doesn't help that privacy activists are filing official complaints arguing Facebook doesn't comply with GDPR.

Read Facebook's official statement here.

 

Top industry experts will offer a range of information and insight on who the bad guys are – and why they might be targeting your enterprise. Click for more information

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.