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.

Vulnerabilities / Threats

6/5/2012
04:21 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Google Issues Warnings For State-Sponsored Attacks

Google plans to let users know when government-sponsored hackers may be trying to hijack Google accounts.

Google said it will begin warning users when it believes their accounts could be targeted by state-sponsored cyber attacks.

The company plans to post a pink warning banner below its black navigation bar when it has specific intelligence or indications from its own monitoring systems that a state-sponsored attacker may be attempting to hijack users' accounts.

Google warning

How can Google tell a country is behind a specific attack? Google won't say.

"You might ask how we know this activity is state-sponsored," said Google VP of security engineering Eric Grosse in a blog post, "We can't go into the details without giving away information that would be helpful to these bad actors, but our detailed analysis--as well as victim reports--strongly suggest the involvement of states or groups that are state-sponsored."

[ Google is dealing with a lot of security issues. Read Google Apps Security Beat By CloudFlare Hackers. ]

Grosse said that its warning does not necessarily mean that a user's account has been compromised. It just means you may be a target and that you should take steps to ensure your account is secure, he said.

Google will not say whether it will report on the cyber-activities of all countries, including the U.S. and Israel, or whether certain countries get a free pass. U.S. and Israeli involvement in the creation of the Stuxnet malware was recently confirmed in a New York Times report.

"We're going to decline to comment on the make-up of the countries that are involved," a Google spokesperson said in an email. "This is because these warnings are not a response to any particular attack or campaign. Our goal is to warn users and encourage good account security practices."

Such practices include enabling two-step authentication in Google Apps, choosing strong passwords, and keeping your software up-to-date, to name a few.

The one country sure to be included on the list of countries that Google monitors is China, a country mentioned in several Google posts about security issues in recent years, though never directly accused.

In January 2010, Google said it had "detected a highly sophisticated and targeted attack on our corporate infrastructure originating from China that resulted in the theft of intellectual property from Google."

And in June 2011, Google warned of a campaign to collect Gmail passwords and said the attack "appears to originate from Jinan, China, affected what seem to be the personal Gmail accounts of hundreds of users including, among others, senior U.S. government officials, Chinese political activists, officials in several Asian countries (predominantly South Korea), military personnel and journalists."

Though Google did not directly accuse the Chinese government of involvement in these attacks, the Chinese government reacted as if it did. Following Google's Gmail attack warning, a Chinese foreign ministry spokesperson said it was unacceptable to blame China.

On a related note, Google last month said that it would notify mainland China users of its Hong Kong-based search service "when they enter a keyword that may cause connection issues." Connection issues often happen in mainland China as a result of government-mandated censorship.

Employees and their browsers might be the weak link in your security plan. The new, all-digital Endpoint Insecurity Dark Reading supplement shows how to strengthen them. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...