Welcome Guest. | Log In| Register | Membership Benefits
  • Email this page E-mail this page
  • |  Print Print this page
  • |   Bookmark and Share

No New Payment Processor Data Breach After All

Visa says notice to card issuers was part of a known breach, but won't reveal which one

Mar 02, 2009 | 01:56 PM

By Kelly Jackson Higgins
DarkReading

Turns out word about a new payment-card processor data breach was a false alarm: After several credit unions posted notices in the past couple of weeks warning that Visa had alerted them to a new payment processor breach, Visa now says the alerts were related to an existing, known breach.

"The recent alerts Visa sent to card issuers were part of an existing investigation and are not related to a new compromise event," Visa said in a statement issued late last week.

But Visa wouldn't say just what organization or breach it was referring to.

Financial institutions had been on alert for another possible payment processor breach separate from Heartland Payment Systems and RBS WorldPay. Several credit unions and organizations posted warnings on their Websites, including the Community Bankers Association of Illinois, the Tuscaloosa VA Federal Credit Union, and the Pennsylvania Credit Union Association. The Open Security Foundation also posted a notice on its DataLossDB Website.

The organizations said they had been alerted by Visa and MasterCard that the breach had exposed so-called card-not-present transactions (online and call-based transactions), rather than magnetic-strip track data. Primary account numbers and expiration dates were stolen from the firm's settlement system, according to these reports. "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 Tuscaloosa VA Federal Credit Union said on its site.

Word of a possible third payment-processor hack came just weeks after Heartland Payment Systems' disclosure on Jan. 20 that it had discovered malware on its servers. Heartland, which is under investigation by various government entities, including the Department of Justice and the Federal Trade Commission, processes 100 million payment card transactions per month for 175,000 merchants.

Meanwhile, it's unclear what caused all of the confusion about the latest credit card breach warnings, which led to Visa's issuing a public statement that there was no new hack.

"Visa has provided the affected accounts to financial institutions so they can take steps to protect consumers. In addition, Visa is risk-scoring all transactions in real-time, helping card issuers better distinguish fraud transactions from legitimate ones," Visa said in its statement.

"It's essential that every business that handles payment card information adhere to the highest data protection standards to protect the security and privacy of their customers' financial information. Visa is aggressively partnering with businesses and financial institutions to enhance security surrounding debit, credit and prepaid card information," the statement said.

MasterCard, meanwhile, said in a statement that it is "monitoring developments" in this case and has notified the affected card issuers. "Because this incident is the subject of an ongoing investigation, we cannot disclose additional details regarding the incident or otherwise comment at this time," the company said.

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


Subscribe to RSS










Bugs
ENTERPRISE VULNERABILITIES
Vulnerability:suse linux
Published:2010-01-22
Severity:High
Description:SUSE Linux Enterprise 10 SP3 (SLE10-SP3) configures postfix to listen on all network interfaces, which might allow remote attackers to bypass intended access restrictions.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:The URL validation functionality in Microsoft Internet Explorer 7 and 8 does not properly process input parameters, which allows remote attackers to execute arbitrary local programs via a crafted URL, aka "URL Validation Vulnerability."
Vulnerability:bind
Published:2010-01-22
Severity:Medium
Description:ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P5, 9.5 before 9.5.2-P2, 9.6 before 9.6.1-P3, and 9.7.0 beta does not properly validate DNSSEC (1) NSEC and (2) NSEC3 records, which allows remote attackers to add the Authenticated Data (AD) flag to a forged NXDOMAIN response for an existing domain.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:Microsoft Internet Explorer 6, 6 SP1, 7, and 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-2530 and CVE-2009-2531.
Vulnerability:ie
Published:2010-01-22
Severity:High
Description:Microsoft Internet Explorer 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly initialized or (2) is deleted, leading to memory corruption, aka "Uninitialized Memory Corruption Vulnerability," a different vulnerability than CVE-2009-3671, CVE-2009-3674, and CVE-2010-0246.


Briefing Centers
POWERFUL INFORMATION
AT YOUR FINGERTIPS
(SPONSORED LINKS)