Vulnerabilities / Threats

6/8/2018
11:35 AM
50%
50%

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
Newest First  |  Oldest First  |  Threaded View
Why CISOs Need a Security Reality Check
Joel Fulton, Chief Information Security Officer for Splunk,  6/13/2018
Cisco Talos Summit: Network Defenders Not Serious Enough About Attacks
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/13/2018
Four Faces of Fraud: Identity, 'Fake' Identity, Ransomware & Digital
David Shefter, Chief Technology Officer at Ziften Technologies,  6/14/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-8030
PUBLISHED: 2018-06-20
A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 7.0.0-7.0.4 when AMQP protocols 0-8, 0-9 or 0-91 are used to publish messages with size greater than allowed maximum message size limit (100MB by default). The broker crashes due to the defect. AMQP protocols 0-10 and 1.0 a...
CVE-2018-1117
PUBLISHED: 2018-06-20
ovirt-ansible-roles before version 1.0.6 has a vulnerability due to a missing no_log directive, resulting in the 'Add oVirt Provider to ManageIQ/CloudForms' playbook inadvertently disclosing admin passwords in the provisioning log. In an environment where logs are shared with other parties, this cou...
CVE-2018-11701
PUBLISHED: 2018-06-20
FastStone Image Viewer 6.2 has a User Mode Write AV at 0x005cb509, triggered when the user opens a malformed JPEG file that is mishandled by FSViewer.exe. Attackers could exploit this issue for DoS (Access Violation) or possibly unspecified other impact.
CVE-2018-11702
PUBLISHED: 2018-06-20
FastStone Image Viewer 6.2 has a User Mode Write AV at 0x00578cb3, triggered when the user opens a malformed JPEG file that is mishandled by FSViewer.exe. Attackers could exploit this issue for DoS (Access Violation) or possibly unspecified other impact.
CVE-2018-11703
PUBLISHED: 2018-06-20
FastStone Image Viewer 6.2 has a User Mode Write AV at 0x00402d6a, triggered when the user opens a malformed JPEG file that is mishandled by FSViewer.exe. Attackers could exploit this issue for DoS (Access Violation) or possibly unspecified other impact.