Endpoint

4/19/2017
01:30 PM
100%
0%

InterContinental Hotels Group Breach Checks In at 1,200 Locations

IHG franchises in its Americas region were hit with a point-of-sale malware breach, affecting 1,200 hotels ranging from its Crowne Plaza to Holiday Inn Express.

InterContinental Hotels Group franchisees were hit with malware on their point-of-sale systems (POS), which allowed cyberthieves to make off with credit cardholder names, card numbers, expiration dates and back-of-the-card security numbers at 1,200 IHG locations in the Americas.

The breach occurred from Sept. 29 to Dec. 29 at IHG franchises, ranging from the Crowne Plaza to its Holiday Inn Express, IHG announced late last week. And although it did not list the scope of the breach, Data Breach Today reported 1,200 locations were affected.

IHG became aware of the breach after its franchisees began getting notices from payment card networks that their customers were incurring unauthorized charges after having used their credit cards at IHG hotels. IHG's investigation found malware on POS systems was capturing credit card information used at the front desk of a number of its franchisees' hotels.

According to IHG, hotels that loaded its point-to-point encryption payment acceptance solution, Secure Payment Solution (SPS), prior to Sept. 29 were not affected by the malware and those that did so after that date found, once it was installed, the malware could not pilfer the information on the card.

Read more about IHG's breach 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
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/20/2017 | 10:29:19 AM
Reactive Mechanisms
Aside from applying the non-vulnerable malware detection agents, what were the reactive mechanisms utilized if any for the affected users and their sensitive information?
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Lessons from My Strange Journey into InfoSec
Lysa Myers, Security Researcher, ESET,  7/12/2018
What's Cooking With Caleb Sima
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14339
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the MMSE dissector could go into an infinite loop. This was addressed in epan/proto.c by adding offset and length validation.
CVE-2018-14340
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, dissectors that support zlib decompression could crash. This was addressed in epan/tvbuff_zlib.c by rejecting negative lengths to avoid a buffer over-read.
CVE-2018-14341
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the DICOM dissector could go into a large or infinite loop. This was addressed in epan/dissectors/packet-dcm.c by preventing an offset overflow.
CVE-2018-14342
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the BGP protocol dissector could go into a large loop. This was addressed in epan/dissectors/packet-bgp.c by validating Path Attribute lengths.
CVE-2018-14343
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the ASN.1 BER dissector could crash. This was addressed in epan/dissectors/packet-ber.c by ensuring that length values do not exceed the maximum signed integer.