Attacks/Breaches

5/30/2017
10:44 AM
50%
50%

Chipotle Dishes Details on Data Breach

An investigation into the Chipotle security incident announced April 25 confirmed a timeline of attack and type of customer information exposed.

Chipotle has published an update following a security incident announced April 25. It has confirmed malware was used to obtain payment card data from point-of-sale (POS) devices at certain outlets between March 24, 2017 and April 18, 2017.

The Mexican chain restaurant says the malware read payment cards' magnetic stripes as they were routed through POS devices. Malware was designed to search for track data on each card; this includes the card number, expiration date, internal verification code, and sometimes the cardholder's name. There is no sign other customer data was affected in the attack.

Not all restaurants were involved in the breach, and the timeframes of attack vary by location. Chipotle will continue to work with law enforcement and payment card networks so the banks issuing cards can increase monitoring.

Read more details and check affected locations here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RickD012
50%
50%
RickD012,
User Rank: Apprentice
5/30/2017 | 10:22:45 PM
Re: Malware Disclosure
Does anyone know if the malware was on each pos system or at a point where the transactions where aggregated for processing. If on pos systems, was it homegrown pos system or through a pos vendors system like verifone. Also, if on pos systems, how did they get infected if following PCI guidelines
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
5/30/2017 | 12:03:42 PM
Malware Disclosure
Was there any data provided indicating what type of malware was utilized during the incident?
Government Shutdown Brings Certificate Lapse Woes
Curtis Franklin Jr., Senior Editor at Dark Reading,  1/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6443
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. Because of a bug in ctl_getitem, there is a stack-based buffer over-read in read_sysvars in ntp_control.c in ntpd.
CVE-2019-6444
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. process_control() in ntp_control.c has a stack-based buffer over-read because attacker-controlled data is dereferenced by ntohl() in ntpd.
CVE-2019-6445
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can cause a NULL pointer dereference and ntpd crash in ntp_control.c, related to ctl_getitem.
CVE-2019-6446
PUBLISHED: 2019-01-16
An issue was discovered in NumPy 1.16.0 and earlier. It uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, as demonstrated by a numpy.load call.
CVE-2019-6442
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. An authenticated attacker can write one byte out of bounds in ntpd via a malformed config request, related to config_remotely in ntp_config.c, yyparse in ntp_parser.tab.c, and yyerror in ntp_parser.y.