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.

Operational Security //

Data Leakage

1/4/2019
02:30 PM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

Marriott Revises Data Breach Numbers as Investigation Continues

Marriott has revised the number of customer accounts it believes were affected during a massive data breach. While the overall number dropped, the company now believes 5 million unencrypted passport numbers were exposed.

Marriott is still coming to grips with a massive data breach that affected millions of the company's Starwood customers, and the company is now offering further details on what records have been exposed.

First, the good news: In a January 4 release, the company stated it now believes that instead of the original 500 million accounts compromised during the breach, there were actually fewer than 383 million Starwood customer accounts involved.

Marriott also notes: "This does not, however, mean that information about 383 million unique guests was involved, as in many instances, there appear to be multiple records for the same guest."

(Source: iStock)
(Source: iStock)

The compromised data includes guests' mailing addresses, phone numbers, email addresses, passport numbers, Starwood Preferred Guest ("SPG") account information, dates of birth, genders, arrival and departure information, reservation dates and communication preferences. The entire incident remains under investigation by Marriott, several security firms and law enforcement, and how exactly the breach happened remains a mystery.

Still, the update included some bleak news. Specifically, the hotel chain did find that 5.25 million unencrypted passport numbers were stolen during the breach, and that whoever was behind the attack also accessed about 20.3 million encrypted passport numbers, as well. Marriott believes that the master key to decrypt those numbers remained secured.

Finally, the company is estimating that 8.6 million encrypted card payments were compromised, although 354,000 payment cards had expired by September 2018. While these cards appeared to have been secured, Marriott is trying to assess whether the 15- or 16-digit numbers were entered into different data fields within its systems and possibly unencrypted or compromised.

While the Marriott data breach appears to have occurred in 2014, the company's IT team only discovered the event in September, when a security tool noticed an anomaly within the network. After a two-month investigation, the company announced the breach and began alerting customers in November. (See Marriott: 500 Million Guest Records Compromised in Data Breach.)

Later, a New York Times report found that Chinese cyber spies are suspected of orchestrating the breach, specifically to gain access to passport numbers that were stored within the company's databases in order to help build profiles of certain US citizens. (See China Suspected of Massive Marriott Data Breach Report.)

Marriott bought the Starwood hotel chain, which includes Westin, Sheraton, The Luxury Collection, Four Points by Sheraton, W Hotels, St. Regis, Le Méridien, Aloft, Element, Tribute Portfolio and Design Hotels, as well as timeshare properties, in 2015. A separate security breach was reported a few days after the sale. (See Marriott's Due Diligence Failure Led to Massive Data Breach.)

As part of Friday's announcement, Marriott noted that it has now phased out the Starwood reservations database, and all guest reservations are now booked through the company's main network.

The company continues to have a dedicated website for customers who need information and want to ask questions, and Marriott is also offering credit monitoring for guests who were affected.

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-38562
PUBLISHED: 2021-10-18
Best Practical Request Tracker (RT) 4.2 before 4.2.17, 4.4 before 4.4.5, and 5.0 before 5.0.2 allows sensitive information disclosure via a timing attack against lib/RT/REST2/Middleware/Auth.pm.
CVE-2021-41611
PUBLISHED: 2021-10-18
An issue was discovered in Squid 5.0.6 through 5.1.x before 5.2. When validating an origin server or peer certificate, Squid may incorrectly classify certain certificates as trusted. This problem allows a remote server to obtain security trust well improperly. This indication of trust may be passed ...
CVE-2021-42565
PUBLISHED: 2021-10-18
myfactory.FMS before 7.1-912 allows XSS via the UID parameter.
CVE-2021-42566
PUBLISHED: 2021-10-18
myfactory.FMS before 7.1-912 allows XSS via the Error parameter.
CVE-2021-36097
PUBLISHED: 2021-10-18
Agents are able to lock the ticket without the "Owner" permission. Once the ticket is locked, it could be moved to the queue where the agent has "rw" permissions and gain a full control. This issue affects: OTRS AG OTRS 8.0.x version: 8.0.16 and prior versions.