New Google+ bug exposed personal information of 52 million users

&Tab;&Tab;<div class&equals;"wpcnt">&NewLine;&Tab;&Tab;&Tab;<div class&equals;"wpa">&NewLine;&Tab;&Tab;&Tab;&Tab;<span class&equals;"wpa-about">Advertisements<&sol;span>&NewLine;&Tab;&Tab;&Tab;&Tab;<div class&equals;"u top&lowbar;amp">&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;<amp-ad width&equals;"300" height&equals;"265"&NewLine;&Tab;&Tab; type&equals;"pubmine"&NewLine;&Tab;&Tab; data-siteid&equals;"111265417"&NewLine;&Tab;&Tab; data-section&equals;"2">&NewLine;&Tab;&Tab;<&sol;amp-ad>&NewLine;&Tab;&Tab;&Tab;&Tab;<&sol;div>&NewLine;&Tab;&Tab;&Tab;<&sol;div>&NewLine;&Tab;&Tab;<&sol;div><p>Google’s social media platform Google&plus; has suffered a fresh data leak&comma; compromising the personal information of more than 50 million users&period;<&sol;p>&NewLine;<p>The tech giant responded by bringing forward the closure of the under-loved Google&plus; service by four months&comma; shuttering it in April rather than August as it had planned&period;<&sol;p>&NewLine;<p>In a blog post on Monday&comma; Google said the flaw affected 52&period;5 million users who could have had profile information like their name&comma; email address&comma; occupation&comma; and age exposed to developers&comma; even if their account was set to private&period;<&sol;p>&NewLine;<p>It is the second data leak for Google&plus; this year&comma; coming after the company revealed in October it had found a security flaw potentially affecting half a million users&period; The first bug was discovered in March but not announced publicly for more than six months&comma; prompting concerns around transparency&period;<&sol;p>&NewLine;<p>At that point the company announced it would shut down Google&plus; in August but after the latest breach it will now close in April for consumers and within 90 days for developers using Google&plus; API &period;<&sol;p>&NewLine;<blockquote><p>With the discovery of this new bug&comma; we have decided to expedite the shut-down<&sol;p><&sol;blockquote>&NewLine;<p>&OpenCurlyDoubleQuote;With the discovery of this new bug&comma; we have decided to expedite the shut-down&comma;” Google’s vice president of project management David Thacker said in the blog post&period; He added&colon;<&sol;p>&NewLine;<p>&OpenCurlyDoubleQuote;While we recognise there are implications for developers&comma; we want to ensure the protection of our users&period;”<&sol;p>&NewLine;<p>Mr Thacker said the leak was discovered by the company through regular testing and it was only live from November 7-13 before it was patched&period;<&sol;p>&NewLine;<p>That means third parties could have had improper access for six days but Google said they have found no evidence the bug was exploited or data misused&period; The flaw did not expose financial data&comma; passwords&comma; or national identity numbers&comma; Google said&period;<&sol;p>&NewLine;&Tab;&Tab;&Tab;<div style&equals;"padding-bottom&colon;15px&semi;" class&equals;"wordads-tag" data-slot-type&equals;"belowpost">&NewLine;&Tab;&Tab;&Tab;&Tab;<div id&equals;"atatags-dynamic-belowpost-68e3a9a8380ec">&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;<script type&equals;"text&sol;javascript">&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;window&period;getAdSnippetCallback &equals; function &lpar;&rpar; &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;if &lpar; false &equals;&equals;&equals; &lpar; window&period;isWatlV1 &quest;&quest; false &rpar; &rpar; &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&sol;&sol; Use Aditude scripts&period;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;window&period;tudeMappings &equals; window&period;tudeMappings &vert;&vert; &lbrack;&rsqb;&semi;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;window&period;tudeMappings&period;push&lpar; &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;divId&colon; 'atatags-dynamic-belowpost-68e3a9a8380ec'&comma;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;format&colon; 'belowpost'&comma;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub; &rpar;&semi;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub;&NewLine;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;if &lpar; document&period;readyState &equals;&equals;&equals; 'loading' &rpar; &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;document&period;addEventListener&lpar; 'DOMContentLoaded'&comma; window&period;getAdSnippetCallback &rpar;&semi;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub; else &lbrace;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;window&period;getAdSnippetCallback&lpar;&rpar;&semi;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;&Tab;&rcub;&NewLine;&Tab;&Tab;&Tab;&Tab;&Tab;<&sol;script>&NewLine;&Tab;&Tab;&Tab;&Tab;<&sol;div>&NewLine;&Tab;&Tab;&Tab;<&sol;div>


Discover more from London Glossy Post

Subscribe to get the latest posts sent to your email.

- Advertisement -
Exit mobile version