{"id":15358,"date":"2019-05-20T20:30:32","date_gmt":"2019-05-21T04:30:32","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2019\/05\/20\/news-9107\/"},"modified":"2019-05-20T20:30:32","modified_gmt":"2019-05-21T04:30:32","slug":"news-9107","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2019\/05\/20\/news-9107\/","title":{"rendered":"Top 10 epic Facebook fails"},"content":{"rendered":"<p><strong>Credit to Author: Marina Mash| Date: Mon, 20 May 2019 15:10:30 +0000<\/strong><\/p>\n<p>This May, Mark Zuckerberg celebrated his 35th birthday. Congratulations! Zuckerberg did not make it to this milestone quietly, however. Instead, he faces a federal investigation <a href=\"https:\/\/www.washingtonpost.com\/technology\/2019\/04\/19\/federal-investigation-facebook-could-hold-mark-zuckerberg-accountable-privacy-sources-say\/?utm_term=.cf91a4d9afcc\" target=\"_blank\" rel=\"noopener noreferrer\">looking<\/a> at ways to hold him personally accountable for mismanaging users&#8217; private data while Facebook-related scandals keep making headlines. In this post we have compiled Facebook&#8217;s 10 most prominent fails involving data misuse.<\/p>\n<p> <a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2019\/05\/20110522\/facebook-10-fails-featured.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-26981\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2019\/05\/20110522\/facebook-10-fails-featured.jpg\" alt=\"\" width=\"1460\" height=\"960\" \/><\/a> <\/p>\n<h2>1. Cambridge Analytica: How it all began<\/h2>\n<p>It all started with the Cambridge Analytica scandal. Back in early 2018 we all learned for the first time with 100% certainty that the data and opinions we share across Facebook can be used by a third party without our consent. Cambridge Analytica&#8217;s harvesting of the data of 50 million Facebook users and its use of that data for political advertising shook the world, but it was only the beginning. To review those events, you can read <a href=\"https:\/\/www.kaspersky.com\/blog\/delete-facebook\/21772\/\" target=\"_blank\" rel=\"noopener noreferrer\">this post<\/a>.<\/p>\n<h2>2. Facebook tokens stolen<\/h2>\n<p>Half a year later, <a href=\"https:\/\/www.kaspersky.com\/blog\/facebook-token-breach\/24052\/\" target=\"_blank\" rel=\"noopener noreferrer\">another scandal caught up with Facebook<\/a>: Hijackers were able to exploit several vulnerabilities in Facebook and steal the access tokens (which are basically an equivalent of digital keys that keep people logged in) of millions of Facebook users.<\/p>\n<p>In total, 30 million users had their tokens stolen. For\u00a015 million, malefactors accessed\u00a0their names and contact details. In 14 million cases, the attackers were able to see more detailed info and the users&#8217; Facebook activities. For\u00a0the remaining 1 million, the hijackers did not access any information. That was when Facebook users learned that Facebook is not impregnable and that their accounts could be stolen en masse without them doing anything wrong.<\/p>\n<p> <input type=\"hidden\" class=\"category_for_banner\" value=\"kis-trial-privacy\" \/> <\/p>\n<h2>3. Facebook and Instagram passwords exposed<\/h2>\n<p>If 30 million wasn&#8217;t enough, another incident came along involving hundreds of millions of Facebook and Instagram users. In early 2019, Facebook made us aware that its internal processes related to user data security are far from perfect. The company admitted it <a href=\"https:\/\/newsroom.fb.com\/news\/2019\/03\/keeping-passwords-secure\/\" target=\"_blank\" rel=\"noopener noreferrer\">was storing<\/a> part of the passwords for Facebook and Instagram accounts in plain text. They insisted these passwords were visible to employees only and that no one abused their access permissions.<\/p>\n<p>At this point, the exact number of affected users has not been disclosed. First, the company commented that the problem involved hundreds of millions of Facebook Lite users, tens of millions of regular Facebook users, and tens of thousands of Instagram users. One month later, it amended its comment to say the issue (now patched) affected not tens of thousands, but millions of Instagram users.<\/p>\n<h2>4. Instagram passwords exposed again<\/h2>\n<p>Actually, that was not the first time Instagram users learned they could&#8217;ve had their passwords leaked. Several months earlier, Instagram&#8217;s &#8220;Download Your Data&#8221; feature was discovered to contain <a href=\"https:\/\/www.theverge.com\/2018\/11\/17\/18100235\/instagram-security-bug-exposed-user-passwords-data-download-tool\" target=\"_blank\" rel=\"noopener noreferrer\">a security flaw<\/a> (now patched) that could have inadvertently exposed some Instagram passwords. If someone submitted their login information to use the feature, their password was included in a URL in their Web browsers and \u2014 again \u2014 stored on Facebook&#8217;s servers in plain text.<\/p>\n<h2>5. Facebook requested e-mail passwords and scraped contacts<\/h2>\n<p>Facebook scraped the e-mail contacts of 1.5 million users without their consent. Wait, it&#8217;s actually a bit more complicated than that. Here&#8217;s the story: Facebook was <a href=\"https:\/\/twitter.com\/originalesushi\/status\/1112496649891430401\" target=\"_blank\" rel=\"noopener noreferrer\">asking<\/a> a subset of newcomers to verify their identities by providing passwords to their e-mail accounts. When the news broke, many thought it was an April Fool&#8217;s joke; no savvy Internet surfer could even imagine granting a third party access to their e-mail communications. Unfortunately, it was not a joke. And many fell for it.<\/p>\n<p>Facebook <a href=\"https:\/\/www.businessinsider.com\/facebook-uploaded-1-5-million-users-email-contacts-without-permission-2019-4\" target=\"_blank\" rel=\"noopener noreferrer\">insisted<\/a> it didn&#8217;t access the contents of the users&#8217; e-mails, just \u2014 unintentionally \u2014 scooped up their e-mail contacts. In total, the address books of 1.5 million users have been harvested. But given that people&#8217;s contact lists may have hundreds of contacts, the final number of those whose contact details were obtained this way may well be in the tens of millions. The company says it used the data to improve ad targeting, build Facebook&#8217;s web of social connections, and recommend new friends to users.<\/p>\n<h2>6. 2FA with Facebook, a tool for advertisers<\/h2>\n<p>Of course, we all want to keep our accounts safe, and two-factor authentication seems like an ideal way to do that. But even here, potential issues arise. For example, the phone number you provide when enabling two-factor authentication for your Facebook account will be automatically associated with your profile \u2014 without an opt-out option. As a result, anyone, regardless of whether they even have an account, can <a href=\"https:\/\/techcrunch.com\/2019\/03\/03\/facebook-phone-number-look-up\/\" target=\"_blank\" rel=\"noopener noreferrer\">look up<\/a> your user profile based on this phone number. Bonus: Facebook <a href=\"https:\/\/www.facebook.com\/notes\/facebook-security\/fixing-sms-notifications-for-those-using-two-factor-authentication\/10155124741945766\/\" target=\"_blank\" rel=\"noopener noreferrer\">might also target<\/a> the number with ads.<\/p>\n<h2>7. Your contacts are never safe from advertisers<\/h2>\n<p>As we mentioned tangentially above, Facebook and Instagram <a href=\"https:\/\/gizmodo.com\/facebook-is-giving-advertisers-access-to-your-shadow-co-1828476051\" target=\"_blank\" rel=\"noopener noreferrer\">were giving<\/a> advertisers access to contact information that users hadn&#8217;t even stored on Facebook! In other words, advertisers were (and, probably, still are) targeting us relying not only on the e-mail addresses and phone numbers we indicate on our &#8220;contact and basic info&#8221; page, but also on other data.<\/p>\n<p>This data can include the phone number (if any) you put in for 2FA purposes and the junk e-mail addresses you hand over for discounts or for furtive online shopping. Also, if any of your contacts chooses to share (&#8220;synchronize&#8221;) <em>their<\/em> contacts with Facebook or uploads their address book to Facebook \u2014 to &#8220;find friends&#8221; \u2014 and their contact list includes a phone number of yours, even if you never entered that information anywhere on Facebook, advertisers will be able to target you with an ad using that phone number.<\/p>\n<h2>8. More Facebook data shared with advertisers<\/h2>\n<p>Facebook <a href=\"https:\/\/www.nbcnews.com\/tech\/social-media\/mark-zuckerberg-leveraged-facebook-user-data-fight-rivals-help-friends-n994706\" target=\"_blank\" rel=\"noopener noreferrer\">was tapping<\/a> users&#8217; data as leverage over companies it partnered with, leaked internal documents showed. For example, Amazon.com, which was spending significant sums on Facebook advertising, <a href=\"https:\/\/www.nytimes.com\/2018\/12\/18\/technology\/facebook-privacy.html\" target=\"_blank\" rel=\"noopener noreferrer\">could obtain<\/a> users&#8217; names and e-mail addresses through their friends (as could Sony, Microsoft and many others).<\/p>\n<p>Microsoft&#8217;s Bing search engine was allowed to see the names of virtually all of our Facebook friends without our (or their) consent. Netflix, Spotify, and the Royal Bank of Canada were given privileges to read, write, and delete our private messages, and to see all of the participants on a thread. Apple devices had access to the contact numbers and calendar entries even of people who had changed their account settings to disable all sharing.<\/p>\n<p><strong>The companies involved stated they never misused the data they accessed, and some said they didn&#8217;t even know they had such &#8220;extended&#8221; rights.<\/strong><\/p>\n<h2>9. Facebook Marketplace leaked sellers&#8217; exact locations<\/h2>\n<p>A flaw (<a href=\"https:\/\/www.databreachtoday.com\/facebook-marketplace-flaw-revealed-sellers-exact-location-a-12402\" target=\"_blank\" rel=\"noopener noreferrer\">now patched<\/a>) in Facebook&#8217;s digital marketplace was exposing sellers&#8217; exact locations (precise latitude and longitude coordinates), and by extension, their goods. To see the location, it wasn&#8217;t even necessary to log in to Facebook, leading some researchers to call the service &#8220;a shopping list for thieves.&#8221; That was especially worrying for those who were selling expensive bicycles, because those are a tasty morsel for criminals, and Marketplace was basically giving those bikes away to them by exposing the sellers&#8217; location.<\/p>\n<h2><strong>10. Facebook data exposed \u2014 by a third party<\/strong><\/h2>\n<p>Two databases containing Facebook users&#8217; information <a href=\"https:\/\/techcrunch.com\/2019\/04\/03\/facebook-records-exposed-server\/\" target=\"_blank\" rel=\"noopener noreferrer\">were found<\/a> on the open Web, storing the data in plain text, allowing absolutely anyone to access and download it. One set of data came from a Facebook game application called &#8220;At the Pool,&#8221; which fell into disuse a long time ago. The second one, containing more than 540 million records, belonged to Cultura Colectiva, a Mexican media company operating throughout Latin America. Both exposed databases included the names and e-mail addresses of users, their friends&#8217; lists, likes, comments, and all kinds of details that serve as means to analyze preferences and interests.<\/p>\n<p>Although the information was not particularly sensitive, and Facebook&#8217;s own staff had nothing to do with the exposure, it still raised (again) questions of how Facebook is sharing users&#8217; data with third parties, and echoed the Cambridge Analytica scandal that kicked off this post.<\/p>\n<p> <input type=\"hidden\" class=\"category_for_banner\" value=\"kis-trial-cyberattacks\" \/> <\/p>\n<p>If after reading this post you feel you&#8217;ve had enough of Facebook&#8217;s shenanigans, you can find <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-delete-facebook\/25536\/\" target=\"_blank\" rel=\"noopener noreferrer\">instructions on\u00a0how to delete your Facebook account<\/a> on our blog. Of course, that decision is purely up to you.<\/p>\n<p><a href=\"https:\/\/www.kaspersky.com\/blog\/facebook-10-fails\/26980\/\" target=\"bwo\" >https:\/\/blog.kaspersky.com\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p><strong>Credit to Author: Marina Mash| Date: Mon, 20 May 2019 15:10:30 +0000<\/strong><\/p>\n<p>10 Facebook mistakes that threatened users\u2019 security and privacy.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10425,10378],"tags":[3589,14327,16379,5897],"class_list":["post-15358","post","type-post","status-publish","format-standard","hentry","category-kaspersky","category-security","tag-facebook","tag-fails","tag-mistakes","tag-privacy"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/15358","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=15358"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/15358\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=15358"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=15358"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=15358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}