Attacks/Breaches

4/11/2011
04:46 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Yet Another Security Firm Breached: Employee Email, User Accounts Leaked

Barracuda Networks a victim of SQL injection attack on its website that exposed customer lead, partner, and internal user information

Another week, another security firm breach: Hackers have posted employee, partner, and customer credentials stolen from Barracuda Networks in what began with a SQL injection attack on the security firm's website.

UPDATE: Barracuda late tonight confirmed that its corporate website indeed had been hacked via a SQL injection attack, and names and emails of customer and partners, including some hashes of salted passwords, exposed. "However, all active passwords for applications in use remain secure," said Michael Perone, executive vice president and CMO at Barracuda in a blog posting on the security vendor's website.

Perone said the attack occurred when the company's web application firewall was accidentally set in passive monitoring mode during a maintenance period on the site. "So, the bad news is that we made a mistake ... The Barracuda Web Application Firewall in front of the Barracuda Networks Web site was unintentionally placed in passive monitoring mode and was offline through a maintenance window that started Friday night (April 8, 2011) after close of business Pacific time. Starting Saturday night at approximately 5pm Pacific time, an automated script began crawling our Web site in search of unvalidated parameters," he blogged.

The attackers found a SQL injection bug in PHP script in the company's customer case study database, which shared the company's marketing database of customer leads, partners, and some Barracuda employees. "The attack utilized one IP address initially to do reconnaissance and was joined by another IP address about three hours later. We have logs of all the attack activity, and we believe we now fully understand the scope of the attack," Perone blogged.

The hack first came to light earlier today in a public disclosure that was first reported by The Register today, a hacker who goes by "fdf" indicated in a post that he had used a blind SQL injection attack on a Web page for Barracuda customers. Among a list of more than 20 Barracuda databases noted as breached involve marketing; Barracuda University, a training and certification site; MySQL; Live Chat; phpmyadmin; and a database called "leads." Barracuda sells spam and antivirus firewalls, Web filtering hardware, instant messaging firewalls, and traditional firewalls.

Two users' SQL server admin credentials were exposed two users, plus some usernames that had not been in use for years, a Barracuda spokesperson says.

The hacker's post included screen shots of internal Barracuda email addresses and MD5 password hashes, as well as some from Barracuda University and internal live chat login information. The Web server that was hit was a Microsoft IIS 6.0-based platform, according to the disclosure.

Barracuda is the latest in a string of security firms to get hit this year, following HBGary, RSA, and Comodo. "Attackers are clearly targeting security companies. They are able to leverage the information they get for further attacks on their customers," says Chris Wysopal, CTO at Veracode. "It is not known at this time whether that is the intent of these attackers."

Coca-Cola, FedEx, Harvard University, IBM, L'Oreal, and Europcar are all customers of the privately held Barracuda, according to the security vendor's website.

Security experts say based on the screenshots posted on Barracuda by the alleged hackers, the breach appears to be a serious one.

"Barracuda employee password hashes were disclosed to the attackers. It is likely that many of these will be cracked swiftly and that some of these passwords give other access within Barracuda, perhaps through reuse," Wysopal said earlier today, prior to Barracuda's statement.

An older feature in Barracuda's security products for connecting to a customer's device was updated a while back so that the user would have to set up that support connection. But there still might be older versions out that don't have this feature, thus leaving those devices and customers vulnerable to attack, he says. "Since we don't know the intent of the attackers or where else they may have penetrated within Barracuda, it seems prudent to turn off updates until Barracuda can investigate and give the 'all clear' that their update mechanisms were not compromised," Wysopal says.

Wysopal applauded Barracuda's rapid public response to the attack and spelling out what was compromised. "This helps customers gauge how at risk they are when a security product or services provider is compromised. The trend of detailed attack disclosure by security companies such as RSA, HB Gary, and now Barracuda is a positive sign," he says. "My hope is that non-security companies such as Epsilon will do the same so the community can learn what attacks are working."

Meanwhile, the hacker who posted the breach information also gave a shout-out to several other hackers in his post, "Sorcerer," Kill_Tech," Y0y0, Sherina84, Tr4nsltr, Upxilon, Ghimau, otak, "and all Malaysian Hackers."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8980
PUBLISHED: 2019-02-21
A memory leak in the kernel_read_file function in fs/exec.c in the Linux kernel through 4.20.11 allows attackers to cause a denial of service (memory consumption) by triggering vfs_read failures.
CVE-2019-8979
PUBLISHED: 2019-02-21
Koseven through 3.3.9, and Kohana through 3.3.6, has SQL Injection when the order_by() parameter can be controlled.
CVE-2013-7469
PUBLISHED: 2019-02-21
Seafile through 6.2.11 always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.
CVE-2018-20146
PUBLISHED: 2019-02-21
An issue was discovered in Liquidware ProfileUnity before 6.8.0 with Liquidware FlexApp before 6.8.0. A local user could obtain administrator rights, as demonstrated by use of PowerShell.
CVE-2019-5727
PUBLISHED: 2019-02-21
Splunk Web in Splunk Enterprise 6.5.x before 6.5.5, 6.4.x before 6.4.9, 6.3.x before 6.3.12, 6.2.x before 6.2.14, 6.1.x before 6.1.14, and 6.0.x before 6.0.15 and Splunk Light before 6.6.0 has Persistent XSS, aka SPL-138827.