Home / Mobile Phones / Windows Phone / Windows Phone: Facebook#39;s security lapses exposed as 540 million users#39; details become publicly accessible

Windows Phone: Facebook#39;s security lapses exposed as 540 million users#39; details become publicly accessible

Windows Phone:

Facebook’s security woes continue as cybersecurity firm UpGuard recently uncovered detailed information about more than 540 million Facebook users was publicly accessible for months.

According to UpGuard, the massive cache of unprotected data was discovered on unsecured Amazon servers used by a Mexican social media firm.

The data sets that included users’ names, passwords, comments, interests, and likes were uploaded to Amazon’s cloud servers by two different Facebook app developers.

Also Read: Facebook says has made headway against abuses ahead of India election

Facebook apps to stop working on Windows phone from April 30

Political ads spend on Facebook crosses Rs 10 crore; BJP supporters continue to lead

Facebook’s data leaks originated at third-party companies, the first of which was data that belonged to Cultura Colectiva, a Mexican online media platform, while the second breach came from data recorded by the “At the Pool” Facebook game.

Both servers from where the leaks originated housed tons of data in the form of account names, Facebook IDs, comments, user preferences, passwords, list of Facebook friends, reactions and other data used for social media analysis.

In reference to the 22,000 leaked passwords, UpGuard stated; “The passwords are presumably for the ‘At the Pool’ app rather than for the user’s Facebook account, but would put users at risk who have reused the same password across accounts.”

This breach is evidence of Faceboo

Read More

About admin

Check Also

Windows Phone: LinqConnect 4.9.1739 (Trial)

Windows Phone: LinqConnect 4.9.1739 (Trial)

What's new in LinqConnect 4.9.1739: Deprecated design-time Synchronous API calls are no longer used with Visual Studio 2019 and Visual Studio 2017 The bug with executing incorrect SQL request (cached during one of the previous calls), when a variable initialized with an empty collection participates in LINQ query, is fixed The bug with throwing the…

Leave a Reply

Your email address will not be published. Required fields are marked *