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.

Comments
Data Leak Exposes Dow Jones Watchlist Database
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/3/2019 | 7:54:55 PM
Re: S3 again
@Ryan: Which would drain Amazon reseources and drive up the cost of services for the 90+% of cloud customers who are just fine (who in turn will have to drive up their costs to their customers).

At a certain point, trying to protect people against their own stupidity smacks against the law of diminishing returns.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
3/1/2019 | 8:46:53 AM
Re: Time for AWS to make a much needed architectural change to S3
In simple view - gee, no password?  Security genius at work - guess makes life easy doesn't it. 
Kelly White
50%
50%
Kelly White,
User Rank: Author
2/28/2019 | 10:24:04 PM
Time for AWS to make a much needed architectural change to S3
AWS S3 is inherently dangerous. No safety mechanisms built in. Make one mistake and your data is exposed to the internet. It is like driving a car with no seat belts, no airbags, and no crumple zone. Make a single mistake and you will be seriously or even die. That is AWS S3. 

Time for AWS to make completely segmented buckets. Provide internal buckets that are only internal -  no config change can make them external.  And provide external buckets that are external only.  People are going to keep making mistakes. Make this simple change  so that the mistakes aren't so catastrophic.  
kilroy71
50%
50%
kilroy71,
User Rank: Apprentice
2/28/2019 | 9:58:11 PM
Time for AWS tp make an architectursl change
An open file share on an internal network would at most expose the data to employees. Make the same mistake in AWS and it is exposed to the entire internet. AWS S3 Buckets have their purpose, but they really should be hard segmented so that internal buckets are internal only and cannot be public and external buckets are really that -external.

People are going to continue to make mistakes. Time to modify the architecture so that the mistskes are less disasterous.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
2/28/2019 | 7:14:20 PM
Re: S3 again
Yup, and we are going to see this more and more on misconfigured S3 buckets. My advice, when Amazon provides the secure config they should make it so that any changes to their buckets that may decrease security have to be approved by amazon's security team on S3. Otherwise, you are going to continue to see clients of AWS willingly decreasing the S3 security posture because they aren't aware of how to accomplish the desired function without stripping it bare. 
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
2/28/2019 | 2:13:53 PM
S3 again
Geez... ANOTHER data leak on the open cloud! How many years now have we been seeing these headlines?

All the more galling because (1) you generally have to set such things to be public yourself, and (2) this apparently isn't the first time DJ's done this.

Geez...


Greater Focus on Privacy Pays Off for Firms
Robert Lemos, Contributing Writer,  1/27/2020
Average Ransomware Payments More Than Doubled in Q4 2019
Jai Vijayan, Contributing Writer,  1/27/2020
Emerging Long-Range WAN Networks Vulnerable to Hacking, Compromise
Jai Vijayan, Contributing Writer,  1/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Physical Security Privilege Escalation
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-3215
PUBLISHED: 2020-01-29
vtiger CRM 5.4.0 and earlier contain an Authentication Bypass Vulnerability due to improper authentication validation in the validateSession function.
CVE-2019-18634
PUBLISHED: 2020-01-29
In Sudo through 1.8.29, if pwfeedback is enabled in /etc/sudoers, users can trigger a stack-based buffer overflow in the privileged sudo process. (pwfeedback is a default setting in Linux Mint and elementary OS; however, it is NOT the default for upstream and many other packages, and would exist onl...
CVE-2013-2568
PUBLISHED: 2020-01-29
A Command Injection vulnerability exists in Zavio IP Cameras through 1.6.3 via the ap parameter to /cgi-bin/mft/wireless_mft.cgi, which could let a remote malicious user execute arbitrary code.
CVE-2013-2569
PUBLISHED: 2020-01-29
A Security Bypass vulnerability exists in Zavio IP Cameras through 1.6.3 because the RTSP protocol authentication is disabled by default, which could let a malicious user obtain unauthorized access to the live video stream.
CVE-2013-2570
PUBLISHED: 2020-01-29
A Command Injection vulnerability exists in Zavio IP Cameras through 1.6.3 in the General.Time.NTP.Server parameter to the sub_C8C8 function of the binary /opt/cgi/view/param, which could let a remove malicious user execute arbitrary code.