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.

Application Security

5/22/2019
02:00 PM
50%
50%

Google Alerts Admins to Unhashed Password Storage

The company reports it has seen improper access to, or misuse of, affected enterprise G Suite credentials.

Google this week informed a subset of enterprise G Suite users that passwords were stored unhashed in its encrypted internal systems. So far, it says, none of them have been accessed or misused.

The issue specifically affects business G Suite users. Google had previously given domain admins a tool, located in the admin console, to upload or manually set user passwords for employees. This was a commonly requested feature and helped with account recovery and bringing aboard new users. For example, they could use it to give credentials to a new employee on his or her first day. This capability has since been eliminated for password recovery, Google reports in a blog post.

"We made an error when implementing this functionality back in 2005," writes Suzanne Frey, vice president of engineering for Cloud Trust, explaining how the admin console stored copies of the unhashed password. While the passwords were stored in Google's encrypted infrastructure, she says, "this practice did not live up to our standards."

In January 2019, Google was troubleshooting G Suite customer sign-up flows when it found a subset of unhashed passwords mistakenly stored in its encrypted infrastructure. It says it has fixed the issue, alerted those affected, and is working with admins to ensure passwords are reset.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/31/2019 | 10:00:00 PM
Re: Consider everything and everyone as vulnerable
No ones infallible. As you stated. Even titans can fall and Google is most definitely a titan of tech.

 
SharonB187
50%
50%
SharonB187,
User Rank: Author
5/23/2019 | 11:18:30 AM
Consider everything and everyone as vulnerable
It proves that no organization is safe from making security errors. I wonder why this issue was not identified before. 
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19642
PUBLISHED: 2019-12-08
On SuperMicro X8STi-F motherboards with IPMI firmware 2.06 and BIOS 02.68, the Virtual Media feature allows OS Command Injection by authenticated attackers who can send HTTP requests to the IPMI IP address. This requires a POST to /rpc/setvmdrive.asp with shell metacharacters in ShareHost or ShareNa...
CVE-2019-19637
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19638
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function load_pnm at frompnm.c, due to an integer overflow.
CVE-2019-19635
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19636
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_encode_body at tosixel.c.