Attacks/Breaches

8/9/2018
02:20 PM
Connect Directly
Twitter
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
Newest First  |  Oldest First  |  Threaded View
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
6 Reasons Why Employees Violate Security Policies
Ericka Chickowski, Contributing Writer, Dark Reading,  10/16/2018
Getting Up to Speed with "Always-On SSL"
Tim Callan, Senior Fellow, Comodo CA,  10/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Too funny!
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.