Imperva Breach Exposes WAF Customers’ Data, Including SSL Certs, API Keys

Aug 27, 2019

Imperva, one of the leading cybersecurity startups that helps
businesses protect critical data and applications from
cyberattacks, has suffered a data breach that has exposed sensitive
information for some of its customers, the company revealed today.

The security breach particularly affects customers of Imperva’s
Cloud Web Application Firewall (WAF) product, formerly known
as Incapsula, a
security-focused CDN service known for its DDoS mitigation and web
application security features that protect websites from malicious
activities.
^[1]

In a blog
post ^[2] published today, Imperva
CEO Chris Hylen revealed that the company learned about the
incident on August 20, 2019, only after someone informed it about
the data exposure that “impacts a subset of customers of its Cloud
WAF product who had accounts through September 15, 2017.”

The exposed data includes email addresses and hashed and
salted passwords for all Cloud WAF customers who registered before
15th September 2017, as well as API keys and customer-provided SSL
certificates for a subset of users.

“We activated our internal data security response team and
protocol, and continue to investigate with the full capacity of our
resources how this exposure occurred,” the company says.

“We have informed the appropriate global regulatory agencies. We
have engaged outside forensic experts.”

The company has not yet revealed how the Cloud WAF customers’ data
got leaked, whether its servers were compromised or if it was
accidentally left unsecured in a misconfigured database on the
Internet.
However, Imperva is still investigating the incident, and the
company has ensured that it is informing all impacted customers
directly and is also taking additional measures to scale up its
security.

“We profoundly regret that this incident occurred and will continue
to share updates going forward. In addition, we will share
learnings and new best practices that may come from our
investigation and enhanced security measures with the broader
industry,” the company says.

Cloud WAF users are recommended to change their account passwords,
implement Single Sign-On (SSO), enable two-factor authentication
(2FA), generate and upload new SSL certificate, and reset their API
keys.

References

^{^}
Incapsula
(thehackernews.com)
^{^}
blog post
(www.imperva.com)

The Hacker News Headlines

New Apple iOS 16 Exploit Enables Stealthy Cellular Access Under Fake Airplane Mode

Aug 18, 2023

The Hacker News Headlines

China-Linked Bronze Starlight Group Targeting Gambling Sector with Cobalt Strike Beacons

Aug 18, 2023

The Hacker News Headlines

NoFilter Attack: Sneaky Privilege Escalation Method Bypasses Windows Security

Aug 18, 2023

OWASP TOP !0

Injection. Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization. Broken Authentication. Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities temporarily or permanently. Sensitive Data Exposure. Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires special precautions when exchanged with the browser. XML External Entities (XXE). Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks. Broken Access Control. Restrictions on what authenticated users are allowed to do are often not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc. Security Misconfiguration. Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched/upgraded in a timely fashion. Cross-Site Scripting XSS. XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites. Insecure Deserialization. Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks. Using Components with Known Vulnerabilities. Components, such as libraries, frameworks, and other software modules, run with the same privileges as the application. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts. Insufficient Logging & Monitoring. Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.

Imperva Breach Exposes WAF Customers’ Data, Including SSL Certs, API Keys

References

Related Post

New Apple iOS 16 Exploit Enables Stealthy Cellular Access Under Fake Airplane Mode

China-Linked Bronze Starlight Group Targeting Gambling Sector with Cobalt Strike Beacons

NoFilter Attack: Sneaky Privilege Escalation Method Bypasses Windows Security

You missed

Protected: Rotary VI EAST

Protected: BetterCyberCareer Group

Protected: Benin Club 1931 – Official

Protected: Whatsapp AI Automation Group