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...


Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12420
PUBLISHED: 2019-12-12
In Apache SpamAssassin before 3.4.3, a message can be crafted in a way to use excessive resources. Upgrading to SA 3.4.3 as soon as possible is the recommended fix but details will not be shared publicly.
CVE-2019-16774
PUBLISHED: 2019-12-12
In phpfastcache before 5.1.3, there is a possible object injection vulnerability in cookie driver.
CVE-2018-11805
PUBLISHED: 2019-12-12
In Apache SpamAssassin before 3.4.3, nefarious CF files can be configured to run system commands without any output or errors. With this, exploits can be injected in a number of scenarios. In addition to upgrading to SA 3.4.3, we recommend that users should only use update channels or 3rd party .cf ...
CVE-2019-5061
PUBLISHED: 2019-12-12
An exploitable denial-of-service vulnerability exists in the hostapd 2.6, where an attacker could trigger AP to send IAPP location updates for stations, before the required authentication process has completed. This could lead to different denial of service scenarios, either by causing CAM table att...
CVE-2019-5062
PUBLISHED: 2019-12-12
An exploitable denial-of-service vulnerability exists in the 802.11w security state handling for hostapd 2.6 connected clients with valid 802.11w sessions. By simulating an incomplete new association, an attacker can trigger a deauthentication against stations using 802.11w, resulting in a denial of...