Attacks/Breaches
2/23/2009
02:40 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Banks, Credit Card Firms Wait For The Other Shoe To Drop Amid Reports Of Another Payment Processor Breach

Hack of a second U.S.-based payment processing firm exposes accounts used in Internet, phone transactions, according to credit union alerts

Brace yourself for another payment-processor breach: A second U.S.-based payment acquirer/processor has been hit with a network hack that exposed consumers' credit card accounts.

As of this posting, the victim firm's identity had not been revealed. According to several credit unions, Visa recently alerted them that another payment processor had discovered a data breach. Among the credit unions issuing alerts about the breach on their Websites are The Tuscaloosa VA Federal Credit Union and the Pennsylvania Credit Union Association. The Open Security Foundation has a notice posted on its DataLossDB site.

The latest breach follows that of Heartland Payment Systems, which went public on Jan. 20 about discovering malware on its processing system; some security experts have called it the largest security breach ever. Heartland processes 100 million payment card transactions per month for 175,000 merchants.

While details on the latest hack are still emerging, there is one known difference between it and Heartland's: This latest breach exposed so-called card-not-present transactions -- online and call-based transactions -- and not magnetic-stripe track data. Primary account numbers and expiration dates were stolen from the firm's settlement system, according to the Tuscaloosa VA Federal Credit Union.

"As the entity involved has not yet issued a press release, Visa and MasterCard are unable to release the name of the merchant processor. It is important to note that this event is not related to the Heartland Payment Systems breach," the credit union post says.

The accounts were exposed from around February 2008 until August 2008, according to credit card firms, and the breach is likely "significant" but not as large as that of Heartland's. Some cards that were compromised in the Heartland breach may also have been victims of the latest one, reports say.

Security experts, meanwhile, say the similarities between the two attacks are interesting.

"All of my sources indicate a breach, most likely at an acquiring bank/merchant processor. Rumor is it is very similar to the Heartland breach. Based on the attack trends we are seeing, I am highly recommending to my end-user clients that they revise their outbound/egress monitoring and filtering," says Rich Mogull, founder of Securosis. "I also highly suspect we'll see some changes in the next revision of PCI to address this type of attack."

Chris King, director of product marketing for Palo Alto Networks, says these types of attacks will continue to be commonplace until enterprises begin properly managing the applications that run in their networks. And that takes more than complying with PCI. "You have to do more if you want to protect your brand," he says.

In most of the latest high-profile breaches, the threat was found only after the forensics team came into the picture. "Existing network security mechanisms remained clueless," King says."So we've got to get a lot more proactive -- without creating additional impedance for transactions."

Details about the hack remain under wraps for now, and it's unclear how the malware got on the payment processor's systems. "Much of the malware we analyze daily is designed to attack banks. If an employee of the processor logged into the Net from a coffee shop, for example, then this could be one way they got infected with the malware. Once they go back to corporate, the malware is now on the 'inside,'" says Greg Hoglund, CEO of HBGary.

Visa had not responded as of this posting to requests for an interview or comments on the breach.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message Kelly Jackson Higgins is Senior 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 Magazine, ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.