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

Canadian Government Sheds Light On TJX Breach

Attack was conducted via wireless links at two Miami Marshall's stores, investigation reveals

Sep 25, 2007 | 11:45 AM

By Tim Wilson
DarkReading

Since TJX Companies disclosed its massive data breach back in January, hackers, security pros, banks, and victims have all been asking one common question: Exactly how did it happen? (See TJX Breach Skewers Customers, Banks.)

Officially, TJX still isn't telling. But Canadian government investigators this morning issued a report on their findings, which were derived from a nine-month study that received the retail giant's cooperation. The report confirms some earlier news reports, while contradicting others.

The Canadian government investigation confirms that the attackers gained access to TJX data via wireless LANs at two retail stores over a period of many months. The attackers gained access to the data through two Marshall's stores in the Miami area -- not in Minnesota or Massachusetts, as previously reported, officials said.

The wireless LANs were secured only by Wired Equivalent Privacy (WEP), a technology that has been known to be vulnerable for more than a year.

The criminals used the wireless connection to access TJX's Retail Transaction Switch servers, which store information about customer transactions throughout North America. Investigators suspect that the data was collected via some sort of malware, but that the attackers have implemented some method of deleting, removing, or obfuscating the malware, which has made the exact method of attack difficult to pinpoint -- and the criminals impossible to find.

Canadian officials declined to give details on how the tapping of the wireless connections occurred, for fear of giving other hackers ideas on how to do it.

Not surprisingly, the report concludes that TJX did not take sufficient steps to secure or dispose of the sensitive data. The company's upgrade from WEP to WPA took too long, and sufficient encryption was not put in place, it says.

The report also says TJX did not do enough to monitor its systems. The risk of a breach "was foreseeable," the report says, and the company should have been aware of the attack prior to its discovery in December 2006.

"TJX had a duty to monitor its systems vigorously," the report states.

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.

  • Adobe Systems Inc.
  • Secure Computing Corp. (Nasdaq: SCUR)


  • 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)