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
Mexican Voter Database Exposed
Threaded  |  Newest First  |  Oldest First
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/26/2016 | 3:28:11 PM
Security Shortcoming
Would this security shortcoming fall under a blunder of Amazon's or by the entity using their service? Whose involvement lead to the insecure configuration?
PxMx
50%
50%
PxMx,
User Rank: Apprentice
4/27/2016 | 7:30:31 AM
Re: Security Shortcoming
Hard to say, but I would suggest it lands on the entity using the service. Exposure of NoSQL databases has been somewhat common recenlty, this is likely an awareness problem. Developers or administrators may be new to the technology and may not fully understand how to deploy it securely. I've publised an open source database assesment tool to try help prevent situations like this (Github link in my profile). 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/28/2016 | 2:36:53 PM
Re: Security Shortcoming
"... Hard to say, but I would suggest it lands on the entity using the service ..."

I mostly agree but there is always a fine line that overall system not having enough security measures (such as layered) and it is hard to pinpoint. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/28/2016 | 2:39:06 PM
Re: Security Shortcoming
"... Developers or administrators may be new to the technology and may not fully understand how to deploy it securely. ..."

This is an important point I think. We know some of the EC2 outages were because of misconfiguration, they may result into security vulnerabilities too.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/28/2016 | 2:34:36 PM
Re: Security Shortcoming
"... Whose involvement lead to the insecure configuration ..."

Good question, if we could find the answer of this I would say we would find a response to it but most likely both in my view.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/28/2016 | 2:32:44 PM
Voter database private?
I am wondering what private information there would be in a voter database? Name and address? If yes, I would not believe we still consider name and address private.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/28/2016 | 2:45:28 PM
Mexican Voter Database Exposed
 

Another point I would like to make is that sometimes we take one problem and make it very big, this simply be a case that somebody copy/paste the data from Amazon to other systems and that is how it is being exposed. So the vulnerability would be the human mainly not the system.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.