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


News
FluBot Malware's Rapid Spread May Soon Hit US Phones
Kelly Sheridan, Staff Editor, Dark Reading,  4/28/2021
Slideshows
7 Modern-Day Cybersecurity Realities
Steve Zurier, Contributing Writer,  4/30/2021
Commentary
How to Secure Employees' Home Wi-Fi Networks
Bert Kashyap, CEO and Co-Founder at SecureW2,  4/28/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-36124
PUBLISHED: 2021-05-07
Pax Technology PAXSTORE v7.0.8_20200511171508 and lower is affected by XML External Entity (XXE) injection. An authenticated attacker can compromise the private keys of a JWT token and reuse them to manipulate the access tokens to access the platform as any desired user (clients and administrators).
CVE-2020-36125
PUBLISHED: 2021-05-07
Pax Technology PAXSTORE v7.0.8_20200511171508 and lower is affected by incorrect access control where password revalidation in sensitive operations can be bypassed remotely by an authenticated attacker through requesting the endpoint directly.
CVE-2020-36126
PUBLISHED: 2021-05-07
Pax Technology PAXSTORE v7.0.8_20200511171508 and lower is affected by incorrect access control that can lead to remote privilege escalation. PAXSTORE marketplace endpoints allow an authenticated user to read and write data not owned by them, including third-party users, application and payment term...
CVE-2020-36127
PUBLISHED: 2021-05-07
Pax Technology PAXSTORE v7.0.8_20200511171508 and lower is affected by an information disclosure vulnerability. Through the PUK signature functionality, an administrator will not have access to the current p12 certificate and password. When accessing this functionality, the administrator has the opt...
CVE-2020-36128
PUBLISHED: 2021-05-07
Pax Technology PAXSTORE v7.0.8_20200511171508 and lower is affected by a token spoofing vulnerability. Each payment terminal has a session token (called X-Terminal-Token) to access the marketplace. This allows the store to identify the terminal and make available the applications distributed by its ...