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.

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 the Executive Editor of Dark Reading. 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
Oldest First  |  Newest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5292
PUBLISHED: 2020-03-31
Leantime before versions 2.0.15 and 2.1-beta3 has a SQL Injection vulnerability. The impact is high. Malicious users/attackers can execute arbitrary SQL queries negatively affecting the confidentiality, integrity, and availability of the site. Attackers can exfiltrate data like the users' and admini...
CVE-2020-7009
PUBLISHED: 2020-03-31
Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges.
CVE-2019-13495
PUBLISHED: 2020-03-31
In firmware version 4.50 of Zyxel XGS2210-52HP, multiple stored cross-site scripting (XSS) issues allows remote authenticated users to inject arbitrary web script via an rpSys.html Name or Location field.
CVE-2020-5291
PUBLISHED: 2020-03-31
Bubblewrap (bwrap) before version 0.4.1, if installed in setuid mode and the kernel supports unprivileged user namespaces, then the `bwrap --userns2` option can be used to make the setuid process keep running as root while being traceable. This can in turn be used to gain root permissions. Note that...
CVE-2019-14905
PUBLISHED: 2020-03-31
A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS co...