Vulnerabilities / Threats

7/24/2017
03:00 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Weather.com, Fusion Expose Data Via Google Groups Config Error

Companies that leaked data accidentally chose the sharing setting "public on the Internet," which enabled anyone on the Web to access all information contained in the messages

Major companies have publicly exposed messages containing sensitive information due to a user-controlled configuration error in Google Groups.

Researchers at RedLock Cloud Security Intelligence (CSI) discovered Google Groups belonging to hundreds of companies inadvertently exposed personally identifiable information (PII) including customer names, passwords, email and home addresses, salary compensation details, and sales pipeline data. Internal messages also exposed business strategies, which could create competitive risk if in the wrong hands, explains RedLock cofounder and CEO Varun Badhwar.

The Weather Company, the IBM-owned operator of weather.com and intellicast.com, is among the companies affected. Fusion Media Group, parent company of Gizmodo, The Onion, Jezebel, Lifehacker, and other properties made the same mistake.

"The RedLock CSI team only looked for a sample of [Google Groups] cases and found dozens," says Badhwar of this research. "Extending that, there are likely hundreds of companies affected by this misconfiguration."

Google Groups is a G Suite chat application organizations use to create and participate in email-based group chats and online forums. During the configuration process, admins can set the sharing option for "Outside this domain - access to groups" to make messages public or private.

The companies that leaked data accidentally chose the sharing setting "public on the Internet," which enabled anyone on the Web to access all information contained in their messages. RedLock advises all companies using Google Groups to ensure "private" is the sharing setting for "Outside this domain-access to groups."

RedLock's CSI team routinely checks various cloud infrastructure tools for threat vectors, and monitors publicly available data to detect misconfigurations that could cause security incidents, explains Badhwar. To date, the team has found more than 4.8 million exposed records resulting from cloud misconfiguration problems.

This is the latest example of organizations mistakenly exposing data by failing to properly configure their public cloud settings.

Shortly before RedLock announced its findings, a data leak at Dow Jones & Co. exposed millions of customers' personal information due to a configuration error in an Amazon Web Services S3 bucket. The repository had its settings configured to let any AWS authenticated user access its data, making it available to any of the one million users with a free AWS account.

Dow Jones confirmed 2.2 million people were exposed; however, Upguard, which discovered the leak, places that number around four million based on the bucket's size and composition. While Dow Jones has "no reason to believe" any of the data was stolen, its incident is one of many signs that companies are struggling to securely adopt cloud services.

Earlier this year, Upguard discovered Deep Root Analytics accidentally leaked millions of voter records from an unsecured public storage account. Exposed data included phone numbers, birthdates, home and mailing addresses, party affiliation, and self-reported racial background.

The analytics firm, working on behalf of the Republican National Committee, had set its S3 storage bucket files to public instead of private. Most records had permissions to be downloaded and files could be accessed without a password.

"The public cloud can be highly secure when configured correctly, but what we're seeing is there's an overarching learning curve when it comes to how organizations should properly secure cloud applications and public cloud infrastructure," says Badhwar.

Unfortunately, many companies are struggling with basic security. Badhwar says the RedLock CSI team found 40% of organizations have exposed a public cloud resource by incorrectly configuring sharing settings, leading to the recent series of major leaks.

"Simple misconfiguration errors -- whether in SaaS applications or cloud infrastructure -- can have potentially devastating effects," he adds, citing instances of similar mistakes at WWE and Booz Allen Hamilton.

It's important for businesses to teach employees about security practices and tools they can use to automate the process of securing applications, workloads, and systems. Until this education happens, he anticipates we will continue to see these problems.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
_geoff_p_
50%
50%
_geoff_p_,
User Rank: Author
7/25/2017 | 12:39:54 PM
User Error and Permissions Confusion Keeps Being a Problem
Great article! Between accidental oversharing from simple user errors (setting sharing to 'public') and not correctly setting permissions due to potentially confusing nameing schemes ('Any Authenticated AWS User' in Amazon S3 buckets being the latest trend) the cloud is proving that user education continues to be an incredibly important topic. Now instead of clicking a link in a phishing email and accidentally exposing a single system to compromise misconfigured clouds are exposing LARGE quantities of data without the need for external action from potential adversaries.
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8980
PUBLISHED: 2019-02-21
A memory leak in the kernel_read_file function in fs/exec.c in the Linux kernel through 4.20.11 allows attackers to cause a denial of service (memory consumption) by triggering vfs_read failures.
CVE-2019-8979
PUBLISHED: 2019-02-21
Koseven through 3.3.9, and Kohana through 3.3.6, has SQL Injection when the order_by() parameter can be controlled.
CVE-2013-7469
PUBLISHED: 2019-02-21
Seafile through 6.2.11 always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.
CVE-2018-20146
PUBLISHED: 2019-02-21
An issue was discovered in Liquidware ProfileUnity before 6.8.0 with Liquidware FlexApp before 6.8.0. A local user could obtain administrator rights, as demonstrated by use of PowerShell.
CVE-2019-5727
PUBLISHED: 2019-02-21
Splunk Web in Splunk Enterprise 6.5.x before 6.5.5, 6.4.x before 6.4.9, 6.3.x before 6.3.12, 6.2.x before 6.2.14, 6.1.x before 6.1.14, and 6.0.x before 6.0.15 and Splunk Light before 6.6.0 has Persistent XSS, aka SPL-138827.