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.

Attacks/Breaches

8/9/2018
02:20 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

AWS Employee Flub Exposes S3 Bucket Containing GoDaddy Server Configuration and Pricing Models

Publicly accessible S3 bucket included configuration data for tens of thousands of systems, as well as sensitive pricing information.

Editors' note: This article and its headline was updated to correct details about ownership of the S3 bucket and contents therein. 

Another week, another publicly accessible AWS storage cloud found to be leaking enterprise secrets. This time around, the company exposed was GoDaddy – but in a twist on the normal storyline, it was an AWS employee responsible for the misconfiguration. Researchers with the UpGuard Cyber Risk Team today disclosed that they found a publicly accessible Amazon S3 bucket wide open for public consumption.  

Included within that data store were documents that detailed configurations for tens of thousands of systems in the AWS cloud. Additionally, documents with pricing information about these systems were similarly accessible. 

"Essentially, this data mapped a very large scale AWS cloud infrastructure deployment, with 41 different columns on individual systems, as well as summarized and modeled data on totals, averages, and other calculated fields," UpGuard's researchers reported. "Also included were what appear to be GoDaddy's discounts from Amazon AWS, usually restricted information for both parties, who must negotiate for rates."

Exposures such as these have become extremely prevalent. In this year alone, organizations including Accenture, FedEx, and Walmart have all been similarly exposed. Even though Amazon S3 buckets are securely configured by default, many AWS customers tend to turn off security settings for expedience. In an unusual turn of events, this particular exposure was caused not by GoDaddy but by an AWS employee.  

"The bucket in question was created by an AWS salesperson to store prospective AWS pricing scenarios while working with a customer," an Amazon spokesperson said. "No GoDaddy customer information was in the bucket that was exposed. While Amazon S3 is secure by default, and bucket access is locked down to just the account owner and root administrator under default configurations, the salesperson did not follow AWS best practices with this particular bucket.”

According to one study earlier this year by Digital Shadows, researchers estimated that 1.5 billion sensitive files were visible on the internet from misconfigured S3 buckets, NAS devices, FTP servers, and other cloud storage systems.

Configuration information such as that detailed in the exposed documents could potentially provide attackers with a wealth of information, including data about hostname, operating system, memory, CPU, AWS region, and what the specific workloads were being used for. This would be extremely valuable for attackers seeking to map out GoDaddy infrastructure to help direct future malicious activity and find particularly juicy targets. 

However, a spokesperson with GoDaddy explained that the documents exposed were "speculative models from an AWS employee and do not reflect work currently underway with Amazon."

Nevertheless, the pricing data exposed by this incident could have been used for competitive advantage by GoDaddy rivals, technology service vendors, and cloud providers.

"Knowing the details of GoDaddy’s AWS discounts could give others a negotiation advantage and price point that would otherwise be unknown," the report explains. "Furthermore, the way in which GoDaddy allocates their cloud spend is also strategic – this is a blueprint for running cloud infrastructure at the largest scales."

Related Content:

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8966
PUBLISHED: 2020-04-01
There is an Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in php webpages of Tiki-Wiki Groupware. Tiki-Wiki CMS all versions through 20.0 allows malicious users to cause the injection of malicious code fragments (scripts) into a legitimate web page.
CVE-2020-11463
PUBLISHED: 2020-04-01
An issue was discovered in Deskpro before 2019.8.0. The /api/email_accounts endpoint failed to properly validate a user's privilege, allowing an attacker to retrieve cleartext credentials of all helpdesk email accounts, including incoming and outgoing email credentials. This enables an attacker to g...
CVE-2020-11464
PUBLISHED: 2020-04-01
An issue was discovered in Deskpro before 2019.8.0. The /api/people endpoint failed to properly validate a user's privilege, allowing an attacker to retrieve sensitive information about all users registered on the system. This includes their full name, privilege, email address, phone number, etc.
CVE-2020-11465
PUBLISHED: 2020-04-01
An issue was discovered in Deskpro before 2019.8.0. The /api/apps/* endpoints failed to properly validate a user's privilege, allowing an attacker to control/install helpdesk applications and leak current applications' configurations, including applications used as user sources (used for authenticat...
CVE-2020-11466
PUBLISHED: 2020-04-01
An issue was discovered in Deskpro before 2019.8.0. The /api/tickets endpoint failed to properly validate a user's privilege, allowing an attacker to retrieve arbitrary information about all helpdesk tickets stored in database with numerous filters. This leaked sensitive information to unauthorized ...