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.

Cloud Security

// // //

BroadSoft Error Exposes TWC PII on AWS S3

A mis-configured Amazon Web Storage (AWS) instance has once again exposed millions of private customer records to the public Internet. Is it time for companies to re-think the way they're building their AWS buckets?

A mis-configured Amazon Web Storage (AWS) instance has once again exposed millions of private customer records to the public Internet. Is it time for companies to re-think the way they're building their AWS buckets?

This time, unified communications provider <href="https://www.databreaches.net/broadsoft-inc-left-millions-of-partners-customer-data-records-exposed/" target="new">BroadSoft exposed millions of records belonging to the customers of Time-Warner Cable (TWC). According to ThreatPost.com, one file alone contained more than 4 million records featuring, "…user names, Mac addresses, serial numbers, account numbers, service, category details and transaction ID."

BroadSoft's vulnerability is just the latest in a series of private data disasters stemming from mis-configured Amazon S3 buckets. While it's difficult to draw sharp conclusions from a handful of high-profile problems amongst hundreds of thousands of customers, it's quite reasonable to use these cases as the basis for a question: Is there some major flaw either in the mechanism AWS provides for setting up storage buckets or in the process customers use to configure those buckets?

Amazon has pointed out that the default setting for AWS S3 storage is for the bucket to be private -- not advertised on or accessible to the public Internet. In order for breaches of the sort seen lately to occur, someone has to "flip a switch" in the configuration to make the bucket public. There's a step in the process that allows or requires a positive step to be taken -- a step that makes many company and personal secrets not very secret, at all.

Researchers found the two vulnerable buckets when they began test runs after the WWE AWS S3 data breach announced in July. The researchers speculate that engineers set the flag to "public" for testing and never set it back to "private" after testing was completed.

You're invited to attend Light Reading’s LTE Advanced Pro and Gigabit LTE: The Path to 5G event – a free breakfast collocated at Mobile World Congress Americas with a keynote address by Sprint's COO Günther Ottendorfer.

This type of vulnerability has struck, and continues to strike, organizations that may otherwise have very strong data protection procedures in place. In a written statement provided to SecurityNow.com, Virsec Systems Chairman and CEO Atiq Raza said, "It's far too easy for anyone to fire up an Amazon server, select minimal security controls and populate it with sensitive data." He continued, "Well-run organizations with strong internal governance, often share sensitive data with partners, with little assurance that the data will be adequately protected. Enterprises must increasingly accept that they are liable for the actions of their partners, and take a much broader view of information protection."

These recent breaches illustrate just how easy it is for a careless individual or a process that doesn't include positive double-checks on critical settings to leave massive amounts of corporate data exposed. The question for enterprise IT departments is how to protect against these simple, but massively damaging, problems while maintaining the advantages of the cloud.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2022-08-12
Improper input validation on the `contains` LoopBack filter may allow for arbitrary SQL injection. When the extended filter property `contains` is permitted to be interpreted by the Postgres connector, it is possible to inject arbitrary SQL which may affect the confidentiality and integrity of data ...
PUBLISHED: 2022-08-12
undici is an HTTP/1.1 client, written from scratch for Node.js.`undici` is vulnerable to SSRF (Server-side Request Forgery) when an application takes in **user input** into the `path/pathname` option of `undici.request`. If a user specifies a URL such as `` or `//` ```js con...
PUBLISHED: 2022-08-12
BookWyrm is a social network for tracking your reading, talking about books, writing reviews, and discovering what to read next. Some links in BookWyrm may be vulnerable to tabnabbing, a form of phishing that gives attackers an opportunity to redirect a user to a malicious site. The issue was patche...
PUBLISHED: 2022-08-12
This Rails gem adds two methods to the ActiveRecord::Base class that allow you to update many records on a single database hit, using a case sql statement for it. Before version 0.1.3 `update_by_case` gem used custom sql strings, and it was not sanitized, making it vulnerable to sql injection. Upgra...
PUBLISHED: 2022-08-12
Shield is an authentication and authorization framework for CodeIgniter 4. This vulnerability may allow [SameSite Attackers](https://canitakeyoursubdomain.name/) to bypass the [CodeIgniter4 CSRF protection](https://codeigniter4.github.io/userguide/libraries/security.html) mechanism with CodeIgniter ...