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.

Database Security
Authentication
Mobile
Privacy
Compliance
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Imperva Customer Database Exposed
Newest First  |  Oldest First  |  Threaded View
Alexix
50%
50%
Alexix,
 User Rank: Apprentice
9/3/2019 | 12:18:59 PM
Re: More of the same
your are right
tdsan
100%
0%
tdsan,
 User Rank: Ninja
8/29/2019 | 2:29:54 PM
Re: More of the same
Also, the question you have to ask has anyone placed a payload or have they identified any malware communicating back to "command and control" location.

Someone needs to really look into the problem because I am quite sure this is not the end of it.

T
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
8/29/2019 | 1:57:34 PM
Re: More of the same
"the keys have to be regenerated, patches have to be applied, sometimes, users apply the same key so it is going to be interesting how this all plays out."

Yes unless they have been regenerated already they are still at risk even if patch is applied.
Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
8/29/2019 | 1:56:00 PM
Re: More of the same
"but the API keys and SSL certificates, now this is some serious stuff,"

I agree with this, passwords are hashed, what about APIs, SSL/TLS as they are more serious.

 

Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
8/29/2019 | 1:54:00 PM
Re: More of the same
" data breach did not occur 2017 but only exposed data back to that date."

That is true, accounts since Sept 15th 2017. Most likely they were using different system prior to that, or that is when they started the business. :--))

Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
8/29/2019 | 1:51:47 PM
Re: Similar Exposure for Cap One?
"I wonder if the vulnerability in the Capital One WAF that led to their breach has any cross correlation with this exposure?"

I say, it is a good question to ask, obviously.

 

Dr.T
50%
50%
Dr.T,
 User Rank: Ninja
8/29/2019 | 1:50:57 PM
data exposured vs hacked

Not clear, this this data exposed by itself or hacked? Or, we are looking at another human mistake?

 

RyanSepe
50%
50%
RyanSepe,
 User Rank: Ninja
8/29/2019 | 12:00:27 PM
Similar Exposure for Cap One?
I wonder if the vulnerability in the Capital One WAF that led to their breach has any cross correlation with this exposure?
REISEN1955
50%
50%
REISEN1955,
 User Rank: Ninja
8/28/2019 | 10:23:50 AM
Re: More of the same
I read the article in error - data breach did not occur 2017 but only exposed data back to that date.  My apologies.
tdsan
50%
50%
tdsan,
 User Rank: Ninja
8/28/2019 | 8:53:38 AM
Re: More of the same
  • On August 20, 2019, we learned from a third party of a data exposure that impacts a subset of customers of our Cloud WAF product who had accounts through September 15, 2017.
  • Elements of our Incapsula customer database through September 15, 2017, were exposed. These included:
    • email addresses
    • hashed and salted passwords

And for a subset of the Incapsula customers through September 15, 2017:
    • API keys
    • customer-provided SSL certificates

 @Reisen1955 - I am inclined to agree with you, but again. I am not so concerned with the passwords and email addresses, but the API keys and SSL certificates, now this is some serious stuff, the keys have to be regenerated, patches have to be applied, sometimes, users apply the same key so it is going to be interesting how this all plays out.

One thing, since this took place in 2017, how do you account for the damage done to customers within the last two years, that could go into the hundreds of millions.

T


Firms Improve Threat Detection but Face Increasingly Disruptive Attacks
Robert Lemos, Contributing Writer,  2/20/2020
Ransomware Damage Hit $11.5B in 2019
Dark Reading Staff 2/20/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18238
PUBLISHED: 2020-02-26
Moxa ioLogik 2542-HSPA Series Controllers and IOs, and IOxpress Configuration Utility ioLogik 2500 series firmware, Version 3.0 or lower IOxpress configuration utility, Version 2.3.0 or lower. Sensitive information is stored in configuration files without encryption, which may allow an attacker to a...
CVE-2019-17274
PUBLISHED: 2020-02-26
NetApp FAS 8300/8700 and AFF A400 Baseboard Management Controller (BMC) firmware versions 13.x prior to 13.1P1 were shipped with a default account enabled that could allow unauthorized arbitrary command execution via local access.
CVE-2019-17275
PUBLISHED: 2020-02-26
OnCommand Cloud Manager versions prior to 3.8.0 are susceptible to arbitrary code execution by remote attackers.
CVE-2020-3169
PUBLISHED: 2020-02-26
A vulnerability in the CLI of Cisco FXOS Software could allow an authenticated, local attacker to execute arbitrary commands on the underlying Linux operating system with a privilege level of root on an affected device. The vulnerability is due to insufficient validation of arguments passed to a spe...
CVE-2020-3170
PUBLISHED: 2020-02-26
A vulnerability in the NX-API feature of Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause an NX-API system process to unexpectedly restart. The vulnerability is due to incorrect validation of the HTTP header of a request that is sent to the NX-API. An attacker could expl...