Perimeter
Guest Blog // Selected Security Content Provided By Sophos
What's This?
12/15/2011
09:31 AM
Dark Reading
Dark Reading
Security Insights
50%
50%

Criminals Make Sure You're Never Really Alone, Even In Self-Checkout Lanes

Vigilance against card fraud is a 24/7 process, even at the grocery store

Multiple media outlets, such as Wired, have reported that criminals have tampered with the credit- and debit-card readers at self checkouts in more than 20 supermarkets operated by California-based Lucky Supermarkets.

The thieves used credit-card skimmers attached to the terminals to collect the account numbers and PINs of everyone who used them to pay for their groceries.

In announcing the breach, Lucky responsibly advised consumers:

“There have been approximately 80 employee and customer reports of either compromised account data or attempts to access account data, with the majority coming over this past weekend ... We strongly recommend our customers who used a self check-out lane in the affected stores contact their financial institution to close existing accounts and seek further advice. We continue to work with local, state, and federal law enforcement to find those responsible.”

As usual, the theft was discovered only after the damage was done. It turns out an employee performing routine maintenance on a self-checkout machine “uncovered an extra computer board that had been placed inside the checkout machine, recording customers’ financial information.” That was on Nov. 11.

Once the supermarket chain warned customers about the compromise on Nov. 23 -- 12 days later, if you’re keeping score -- the supermarket fielded more than 1,000 calls from customers contending they had been victims of fraud.

The advice by Joseph Steinberg, a security expert whose opinion was solicited for the story states the obvious. “Everyone should always check any device in which they insert/swipe a credit/debit/ATM card, or to which they touch their card, to see if it looks like it may have been modified/covered.”

While it’s impractical that everyone checking themselves out at the local grocer will pay any attention at all to determine whether a credit/debit card machine has been tampered with, most people don't even know what to look for.

In this case it would have been nearly impossible to know these terminals had been altered because the changes were all on the inside, unlike many ATM skimmers that are attached externally.

These are decisions that each of us must make about what kinds of risks we are each willing to tolerate for convenience. You could carry large quantities of cash, but I wouldn't recommend it. For me, I will stick to using my credit card (which offers protection) and leave the debit card and armored truck at home.

Of course, before I insert that credit card I do take a look carefully to see if there is any obvious sign of tampering. I also frequent the same shops and ATMs, which gives me familiarity with what “should” be.

Last, you are not being paranoid if you do these things. They really are out to get us, so remain vigilant.

Chester Wisniewski is a senior security adviser at Sophos Canada

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4807
Published: 2014-11-22
Sterling Order Management in IBM Sterling Selling and Fulfillment Suite 9.3.0 before FP8 allows remote authenticated users to cause a denial of service (CPU consumption) via a '\0' character.

CVE-2014-6183
Published: 2014-11-22
IBM Security Network Protection 5.1 before 5.1.0.0 FP13, 5.1.1 before 5.1.1.0 FP8, 5.1.2 before 5.1.2.0 FP9, 5.1.2.1 before FP5, 5.2 before 5.2.0.0 FP5, and 5.3 before 5.3.0.0 FP1 on XGS devices allows remote authenticated users to execute arbitrary commands via unspecified vectors.

CVE-2014-8626
Published: 2014-11-22
Stack-based buffer overflow in the date_from_ISO8601 function in ext/xmlrpc/libxmlrpc/xmlrpc.c in PHP before 5.2.7 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code by including a timezone field in a date, leading to improper XML-RPC encoding...

CVE-2014-8710
Published: 2014-11-22
The decompress_sigcomp_message function in epan/sigcomp-udvm.c in the SigComp UDVM dissector in Wireshark 1.10.x before 1.10.11 allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted packet.

CVE-2014-8711
Published: 2014-11-22
Multiple integer overflows in epan/dissectors/packet-amqp.c in the AMQP dissector in Wireshark 1.10.x before 1.10.11 and 1.12.x before 1.12.2 allow remote attackers to cause a denial of service (application crash) via a crafted amqp_0_10 PDU in a packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?