Google now minus Google Plus: Social mini-network faces axe in data leak bug drama

Project Zero would have been all over this – yet it remained under wraps


Google has surprised Google+ users – all two of them – by vowing to shutter the service over the next ten months in the wake of a potential data leak.

In what has become an all-too-familiar scenario, the decision is subject to claim and counter-claim: The Wall Street Journal today alleged that Google covered up a programming blunder that would have exposed people's private Google+ account data to app developers, all because the advertising giant didn't want to have to deal with the PR and regulatory fallout from admitting it screwed up.

Meanwhile, Google said the flaw was an unexploited API bug discovered and fixed internally before anyone externally found it – and in any case, it's shuttering Google+ because netizens don't use it. Businesses will still be able to use the service as an internal chat channel, though.

According to a statement today by Google engineering veep Ben Smith, the coding cockup was found in an API review dubbed Project Strobe. Before the bug was fixed, the API could have been exploited by applications connected to Google+ accounts to access the private parts of those profiles. Specifically, third-party applications linked to G+ accounts “had access to Profile fields that were shared with the user, but not marked as public.”

Amusingly, after years of Google PR playing down the small number of active G+ users, it's also now trying to spin that everything's going to be OK because virtually no one used the social network.

Conveyor belt production of jam-topped biscuits. Photo by Shutterstock

UK High Court blocks iPhone Safari privacy suit against Google

READ MORE

The software bug, Smith explained, would only have exposed “name, email address, occupation, gender and age,” if exploited, and not “Google+ posts, messages, Google account data, phone numbers or G Suite content.” The executive noted that while 438 apps could have leveraged the API's security hole, and 500,000 accounts would have been affected in that case, Google's review found “no evidence” that third-party developers had noticed the bug.

The WSJ story quoted unnamed sources that Google chose not to 'fess up to the bug in public because it feared “regulatory scrutiny” and “reputational damage.”

Google's response: “Our Privacy & Data Protection Office reviewed this issue, looking at the type of data involved, whether we could accurately identify the users to inform, whether there was any evidence of misuse, and whether there were any actions a developer or user could take in response. None of these thresholds were met in this instance.”

Regardless of the API gaffe, Google said low user take-up and engagement drove its decision to shutter the normie side of Google+. The service, Smith said, failed both in consumer adoption and engagement with apps: “90 percent of Google+ user sessions are less than five seconds.”

Some infosec bods have taken Google's side, arguing disclosure is only needed if there's evidence of a security breach. Otherwise, it's just another bug fix, in their eyes. Security and privacy researcher Lukasz Olejnik said the story “should not be taken out of proportion” because the bug was “found and fixed.”

Another security researcher, Ryan Satterfield, was even more critical:

On the other hand, of course, Google's Project Zero team publicly skewers organizations and projects that fall short in terms of security, calling out vulnerabilities in products whether they were actively exploited or not. It's perhaps another case of arrogant Google's do-as-we-say, not-as-we-do approach to technology and life. If this were a bug in Facebook discovered by Project Zero, it would have been documented by the team in public for all to see – yet Google kept a lid on its own cockup.

Home improvements

Google's Smith also outlined a slew of other changes pitched as privacy enhancements. These include more granular Google account permissions; limits on apps able to access Gmail accounts; and limits on apps' ability to access Android call logs and text messages.

The most important of these is the change to Gmail access, described in more detail here:

How Data May Not Be Used: 3rd-party apps accessing these APIs must use the data to provide user-facing features and may not transfer or sell the data for other purposes such as targeting ads, market research, email campaign tracking, and other unrelated purposes. (Note: Gmail users’ email content is not used for ads personalization.)

As an example, consolidating data from a user’s email for their direct benefit, such as expense tracking, is a permitted use case. Consolidating the expense data for market research that benefits a third party is not permitted.

We have also clarified that human review of email data must be strictly limited.

Finally, the Android contacts API will no longer let third-party apps access interactions with contacts. ®

Similar topics

Broader topics


Other stories you might like

  • Experts: AI should be recognized as inventors in patent law
    Plus: Police release deepfake of murdered teen in cold case, and more

    In-brief Governments around the world should pass intellectual property laws that grant rights to AI systems, two academics at the University of New South Wales in Australia argued.

    Alexandra George, and Toby Walsh, professors of law and AI, respectively, believe failing to recognize machines as inventors could have long-lasting impacts on economies and societies. 

    "If courts and governments decide that AI-made inventions cannot be patented, the implications could be huge," they wrote in a comment article published in Nature. "Funders and businesses would be less incentivized to pursue useful research using AI inventors when a return on their investment could be limited. Society could miss out on the development of worthwhile and life-saving inventions."

    Continue reading
  • Declassified and released: More secret files on US govt's emergency doomsday powers
    Nuke incoming? Quick break out the plans for rationing, censorship, property seizures, and more

    More papers describing the orders and messages the US President can issue in the event of apocalyptic crises, such as a devastating nuclear attack, have been declassified and released for all to see.

    These government files are part of a larger collection of records that discuss the nature, reach, and use of secret Presidential Emergency Action Documents: these are executive orders, announcements, and statements to Congress that are all ready to sign and send out as soon as a doomsday scenario occurs. PEADs are supposed to give America's commander-in-chief immediate extraordinary powers to overcome extraordinary events.

    PEADs have never been declassified or revealed before. They remain hush-hush, and their exact details are not publicly known.

    Continue reading
  • Stolen university credentials up for sale by Russian crooks, FBI warns
    Forget dark-web souks, thousands of these are already being traded on public bazaars

    Russian crooks are selling network credentials and virtual private network access for a "multitude" of US universities and colleges on criminal marketplaces, according to the FBI.

    According to a warning issued on Thursday, these stolen credentials sell for thousands of dollars on both dark web and public internet forums, and could lead to subsequent cyberattacks against individual employees or the schools themselves.

    "The exposure of usernames and passwords can lead to brute force credential stuffing computer network attacks, whereby attackers attempt logins across various internet sites or exploit them for subsequent cyber attacks as criminal actors take advantage of users recycling the same credentials across multiple accounts, internet sites, and services," the Feds' alert [PDF] said.

    Continue reading

Biting the hand that feeds IT © 1998–2022