Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Wendy's Could Become Test Case For New EMV Liability Rules
Newest First  |  Oldest First  |  Threaded View
jc01480
50%
50%
jc01480,
User Rank: Apprentice
2/3/2016 | 11:12:57 PM
I was one of them...
I am a security professional working at one of the greatest organizations there are. It came as a surprise to me one day when I received an email saying my card had been compromised and a new one was being issued. Within two days I had another (yes, the first one had a chip) EMV card. I haven't verified with my bank as to exactly where this card was compromised, but I speculate it was at Wendy's as my wife and I always ate there on the run like we do. Again, not certain it was them and I'll find out in due course. But so far there is no word from the bank about being charged for the replacement and no indications any money was fraudulently deducted from my account. I give kudos to my financial institution for making me aware and taking measures to cancel the old one while a new one was in my mailbox. So far, my life has not been affected whatsoever by this incident and I hope that the retail industry will adopt the technology required to safeguard retail transactions in lieu of risk mitigation by absorbing the losses. Eventually that risk mitigation will be a red flag to come and get it. And it does speak to the idea of a company's ethics when they are willing to implement this type of behavior because the loss of your PII still wouldn't cost them as much as implementing the technology to prevent it would. Should it be their decision? Just to save them some money? Hopefully this isn't the case for all persons affected. Thanks for reading and happy hunting!
RetiredUser
100%
0%
RetiredUser,
User Rank: Ninja
1/30/2016 | 7:21:47 PM
Re: EMV. Bah.
Past EMV hacks include man-in-the-middle attacks via programming a second chip (FUN card) to accept any PIN entry.  You solder that chip to the card's original chip. This increases the thickness of the chip from 0.4mm to 0.7mm.  This made insertion into a PoS possible (Ars Technia, 2015; researchers Houda Ferradi, Rémi Géraud, David Naccache, and Assia Tria).  Hackers took advantage of PIN authentication at the time being decoupled from transaction verification on EMV cards in Europe.  I'm not up-to-date on how much of this is still possible, but I know it annoys me (the chip) and many are still opposing the idea EMV is inherently safer.
dewald
100%
0%
dewald,
User Rank: Apprentice
1/30/2016 | 1:58:16 PM
Re: EMV. Bah.
"Particularly annoying is the liability shift having come so soon in this process.".  Visa announced the shift in Summer 2011.  Four years is too "soon"?
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
1/30/2016 | 12:06:26 PM
EMV. Bah.
Particularly because studies have indicated that EMV is not inherently safer than magnetic-stripe cards (it simply has different vulnerabilities that are exploited in different ways), and that it has been harder for some defrauded customers to be made whole because credit card companies and merchants automatically assume that EMV is impervious, I am pretty annoyed about EMV being foisted upon us by Visa et al. in the US.

Particularly annoying is the liability shift having come so soon in this process.  The credit-card companies are the ones who foisted this upon us, and they're the ones with the deeper pockets.  I think there was poor policy planning here.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11937
PUBLISHED: 2020-08-06
In whoopsie, parse_report() from whoopsie.c allows a local attacker to cause a denial of service via a crafted file. The DoS is caused by resource exhaustion due to a memory leak. Fixed in 0.2.52.5ubuntu0.5, 0.2.62ubuntu0.5 and 0.2.69ubuntu0.1.
CVE-2020-15114
PUBLISHED: 2020-08-06
In etcd before versions 3.3.23 and 3.4.10, the etcd gateway is a simple TCP proxy to allow for basic service discovery and access. However, it is possible to include the gateway address as an endpoint. This results in a denial of service, since the endpoint can become stuck in a loop of requesting i...
CVE-2020-15136
PUBLISHED: 2020-08-06
In ectd before versions 3.4.10 and 3.3.23, gateway TLS authentication is only applied to endpoints detected in DNS SRV records. When starting a gateway, TLS authentication will only be attempted on endpoints identified in DNS SRV records for a given domain, which occurs in the discoverEndpoints func...
CVE-2020-15701
PUBLISHED: 2020-08-06
An unhandled exception in check_ignored() in apport/report.py can be exploited by a local attacker to cause a denial of service. If the mtime attribute is a string value in apport-ignore.xml, it will trigger an unhandled exception, resulting in a crash. Fixed in 2.20.1-0ubuntu2.24, 2.20.9-0ubuntu7.1...
CVE-2020-15702
PUBLISHED: 2020-08-06
TOCTOU Race Condition vulnerability in apport allows a local attacker to escalate privileges and execute arbitrary code. An attacker may exit the crashed process and exploit PID recycling to spawn a root process with the same PID as the crashed process, which can then be used to escalate privileges....