"We've recently determined that some users were impacted by a software update introduced in November that contained a bug affecting a Google+ API", the company wrote. The vulnerability possibly exposed profile information like names, email addresses, occupations, and ages to developers. It gave outside developers access to user data for six days.
Back in October, Google confirmed that a security bug impacted users of its social network, Google+. Nevertheless, the powers that be have apparently concluded that the site is more trouble than it's worth - and they're probably right, given the scrutiny Google is under.
Google+ has always been the butt of jokes for being a failed social network that few people used.
On Monday, Google said it planned to expedite the closure from August 2019 to April. "We discovered this bug as part of our standard and ongoing testing procedures and fixed it within a week of it being introduced". It's estimated that upwards of 52 million users were affected by this leak. However, the company said there's "no evidence" that any third party compromised Google's systems or misused the data.
Hasenhuttl appears close to being appointed manager of Southampton
The decision comes after the Saints drew 2-2 with Manchester United on Saturday, having led 2-0 during the first half. He also led them to the semi-finals of the FA Cup, where they eventually lost to eventual winners Chelsea.
"In addition, apps with access to a user's Google+ profile data also had access to the profile data that had been shared with the consenting user by another Google+ user but that was not shared publicly", Google added.
"With the discovery of this new bug, we have made a decision to expedite the shutdown of all Google+ APIs [application programming interfaces]; this will occur within the next 90 days", wrote David Thacker, head of product management for G Suite, Google's range of apps offered to businesses.
While Google said it had no evidence either data leak was actively exploited, it has no way of assuring users that developers haven't accessed the profile data that was supposed to be non-public.
The bug impacted approximately 52.5 million users and possibly exposed the aforementioned profile information even when the information was set to not-public.