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.

Attacks/Breaches

8/27/2019
05:00 PM
100%
0%

Imperva Customer Database Exposed

A subset of customers for the company's Incapsula web application firewall had their email addresses, hashed/salted passwords, and more open to unauthorized access, Imperva announced.

Imperva has announced that the cloud web application firewall product formerly called Incapsula suffered a data exposure that allowed unauthorized access to customer data. The company said that a third party informed it on August 20 of the exposure, which affets customers who had Incapsula accounts through September 15, 2017.

According to the notice posted on the CEO's blog, a subset of Incapsula customers had email addresses, hashed and salted passwords, API keys, and customer-provided SSL certificates exposed. The blog post notes that the company is taking a variety of actions addressing the exposure, from engaging forensics experts and informing affected customers to forcing password rotations.

For more, read here.

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "'Culture Eats Policy for Breakfast': Rethinking Security Awareness Training."

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
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
AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4147
PUBLISHED: 2019-09-16
IBM Sterling File Gateway 2.2.0.0 through 6.0.1.0 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 158413.
CVE-2019-5481
PUBLISHED: 2019-09-16
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
CVE-2019-5482
PUBLISHED: 2019-09-16
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
CVE-2019-15741
PUBLISHED: 2019-09-16
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. An unsafe interaction with logrotate could result in a privilege escalation
CVE-2019-16370
PUBLISHED: 2019-09-16
The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.