Attacks/Breaches

2/17/2009
12:26 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Wyndham Hotels Hack Exposes Guest Names, Credit Cards

State Attorney General of Florida warns residents whose accounts may have been compromised to keep an eye on their credit reports for suspicious activity

Another day, another data breach disclosure: This time hotel chain Wyndham Hotels and Resorts (WHR) has revealed that a computer break-in late last summer at one of its franchise hotels exposed guest names and credit card data across 41 of its properties.

Wyndham alerted customers who were affected by the breach just before Christmas, but is now going public with details of the hack. An attacker used a "centralized network connection" at one WHR franchise to access and download information from several WHR properties, and only WHR hotels were affected in the breach, according to the hotel chain, which first discovered the breach in mid-September.

The hotel chain says guest and cardholder names, account numbers, and payment card information were potentially exposed in the hack. The number of Wyndham customer accounts affected by the breach was reported as 21,000 when it was first made public in late December, according to the Open Security Foundation's Data Loss database.

The State Attorney General of Florida yesterday warned state residents affected by the breach to monitor their credit reports for unusual or suspicious activity. Wyndham says affected customers represent a cross-section of its global base. The breach was discovered after the hotel chain noticed "unusual activity" in one of its servers, which was used to siphon data to an "offsite URL," according to Wyndham.

Why the lull in notification of the breach? Wyndham says a full investigation -- including contacting law enforcement -- took eight weeks, and the hotel chain had to match payment card data with contact information of its customers.

"At this time, no criminal identity theft related to the use of the consumer data has been identified. Importantly, we believe that it is unlikely that identity theft will occur because of the limited amount of information that was compromised. Birthdates, SSNs, addresses, or other personally identifying information were not kept by the hotels and therefore not part of the compromise," Wyndham says in a posting on its Website. "Nevertheless, we recommend that you regularly monitor your card and bank statements and that you promptly report all suspicious activity to the financial institution that issued your card."

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 Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Cracking 2FA: How It's Done and How to Stay Safe
Kelly Sheridan, Staff Editor, Dark Reading,  5/17/2018
What Israel's Elite Defense Force Unit 8200 Can Teach Security about Diversity
Lital Asher-Dotan, Senior Director, Security Research and Content, Cybereason,  5/21/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Shhh!  They're watching... And you have a laptop?  
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10593
PUBLISHED: 2018-05-24
A vulnerability in DB Manager version 3.0.1.0 and previous and PerformA version 3.0.0.0 and previous allows an authorized user with access to a privileged account on a BD Kiestra system (Kiestra TLA, Kiestra WCA, and InoqulA+ specimen processor) to issue SQL commands, which may result in data corrup...
CVE-2018-10595
PUBLISHED: 2018-05-24
A vulnerability in ReadA version 1.1.0.2 and previous allows an authorized user with access to a privileged account on a BD Kiestra system (Kiestra TLA, Kiestra WCA, and InoqulA+ specimen processor) to issue SQL commands, which may result in loss or corruption of data.
CVE-2018-11332
PUBLISHED: 2018-05-24
Stored cross-site scripting (XSS) vulnerability in the "Site Name" field found in the "site" tab under configurations in ClipperCMS 1.3.3 allows remote attackers to inject arbitrary web script or HTML via a crafted site name to the manager/processors/save_settings.processor.php f...
CVE-2018-8013
PUBLISHED: 2018-05-24
In Apache Batik 1.x before 1.10, when deserializing subclass of `AbstractDocument`, the class takes a string from the inputStream as the class name which then use it to call the no-arg constructor of the class. Fix was to check the class type before calling newInstance in deserialization.
CVE-2017-17158
PUBLISHED: 2018-05-24
Some Huawei smart phones with the versions before Berlin-L21HNC185B381; the versions before Prague-AL00AC00B223; the versions before Prague-AL00BC00B223; the versions before Prague-AL00CC00B223; the versions before Prague-L31C432B208; the versions before Prague-TL00AC01B223; the versions before Prag...