Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operational Security //

Data Leakage

12/11/2018
07:00 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

New Google+ Bug Affects 52M Users, Accelerating Site's Demise

While the latest disclosure does not seem to have leaked any data, it accelerates Google+'s demise.

The latest nail in the Google+ social media coffin is a newly discovered API bug.

On December 10, Google announced that it had uncovered the API bug during routine testing. Overall, the bug could affect 52.5 million users, although it does not appear that this flaw caused any data to leak.

However, above and beyond any data leaks, the disclosure means that the consumer version of Google+ will now close in April 2019 -- four months earlier than Google previously planned. Additionally, all APIs will cease in the next 90 days.

Google previously announced in October that it would shutter the consumer version of its social media platform, following a disclosure in the Wall Street Journal that found faulty APIs allowing third-party developers to collect data on users. (See Google+ Bug Exposed Personal Data of 500K Users Report.)

However, the enterprise version of the platform will continue.

The latest faulty API was released as part of a routine software update in November.

The issue in this case is that the buggy API would allow apps to collect personal data about users even if the user had his or her settings adjust to "not-public." This could include name, email address, occupation and more.

Additionally, a third-party app could also gather data on users who did not use these applications, but had a friend who did within the social network.

Google did point out that outside developers did not have access to financial data, national identification numbers, passwords, or other data that could be used as part of identity theft.

"We discovered this bug as part of our standard and ongoing testing procedures and fixed it within a week of it being introduced. No third party compromised our systems, and we have no evidence that the app developers that inadvertently had this access for six days were aware of it or misused it in any way," according to Monday's blog post.

As of Monday, Google was in the process of contacting anyone affected by this latest bug.

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
9 Tips to Prepare for the Future of Cloud & Network Security
Kelly Sheridan, Staff Editor, Dark Reading,  9/28/2020
Attacker Dwell Time: Ransomware's Most Important Metric
Ricardo Villadiego, Founder and CEO of Lumu,  9/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20902
PUBLISHED: 2020-10-01
Upgrading Crowd via XML Data Transfer can reactivate a disabled user from OpenLDAP. The affected versions are from before version 3.4.6 and from 3.5.0 before 3.5.1.
CVE-2019-20903
PUBLISHED: 2020-10-01
The hyperlinks functionality in atlaskit/editor-core in before version 113.1.5 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in link targets.
CVE-2020-25288
PUBLISHED: 2020-09-30
An issue was discovered in MantisBT before 2.24.3. When editing an Issue in a Project where a Custom Field with a crafted Regular Expression property is used, improper escaping of the corresponding form input's pattern attribute allows HTML injection and, if CSP settings permit, execution of arbitra...
CVE-2020-25781
PUBLISHED: 2020-09-30
An issue was discovered in file_download.php in MantisBT before 2.24.3. Users without access to view private issue notes are able to download the (supposedly private) attachments linked to these notes by accessing the corresponding file download URL directly.
CVE-2020-25830
PUBLISHED: 2020-09-30
An issue was discovered in MantisBT before 2.24.3. Improper escaping of a custom field's name allows an attacker to inject HTML and, if CSP settings permit, achieve execution of arbitrary JavaScript when attempting to update said custom field via bug_actiongroup_page.php.