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
Threaded  |  Newest First  |  Oldest First
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...
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
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.
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.
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.  
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. 


Commentary
Cyberattacks Are Tailored to Employees ... Why Isn't Security Training?
Tim Sadler, CEO and co-founder of Tessian,  6/17/2021
Edge-DRsplash-10-edge-articles
7 Powerful Cybersecurity Skills the Energy Sector Needs Most
Pam Baker, Contributing Writer,  6/22/2021
News
Microsoft Disrupts Large-Scale BEC Campaign Across Web Services
Kelly Sheridan, Staff Editor, Dark Reading,  6/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-2322
PUBLISHED: 2021-06-23
Vulnerability in OpenGrok (component: Web App). Versions that are affected are 1.6.7 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via HTTPS to compromise OpenGrok. Successful attacks of this vulnerability can result in takeover of OpenGrok. CVSS 3.1 ...
CVE-2021-20019
PUBLISHED: 2021-06-23
A vulnerability in SonicOS where the HTTP server response leaks partial memory by sending a crafted HTTP request, this can potentially lead to an internal sensitive data disclosure vulnerability.
CVE-2021-21809
PUBLISHED: 2021-06-23
A command execution vulnerability exists in the default legacy spellchecker plugin in Moodle 3.10. A specially crafted series of HTTP requests can lead to command execution. An attacker must have administrator privileges to exploit this vulnerabilities.
CVE-2021-34067
PUBLISHED: 2021-06-23
Heap based buffer overflow in tsMuxer 2.6.16 allows attackers to cause a Denial of Service (DoS) by running the application with a crafted file.
CVE-2021-34068
PUBLISHED: 2021-06-23
Heap based buffer overflow in tsMuxer 2.6.16 allows attackers to cause a Denial of Service (DoS) by running the application with a crafted file.