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."

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
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 11/19/2020
New Proposed DNS Security Features Released
Kelly Jackson Higgins, Executive Editor at Dark Reading,  11/19/2020
How to Identify Cobalt Strike on Your Network
Zohar Buber, Security Analyst,  11/18/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: He hits the gong anytime he sees someone click on an email link.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-29071
PUBLISHED: 2020-11-25
An XSS issue was found in the Shares feature of LiquidFiles before 3.3.19. The issue arises from the insecure rendering of HTML files uploaded to the platform as attachments, when the -htmlview URL is directly accessed. The impact ranges from executing commands as root on the server to retrieving se...
CVE-2020-29072
PUBLISHED: 2020-11-25
A Cross-Site Script Inclusion vulnerability was found on LiquidFiles before 3.3.19. This client-side attack requires user interaction (opening a link) and successful exploitation could lead to encrypted e-mail content leakage via messages/sent?format=js and popup?format=js.
CVE-2020-26241
PUBLISHED: 2020-11-25
Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. This is a Consensus vulnerability in Geth before version 1.9.17 which can be used to cause a chain-split where vulnerable nodes reject the canonical chain. Geth's pre-compiled dataCopy (at 0x00...04) co...
CVE-2020-26242
PUBLISHED: 2020-11-25
Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. In Geth before version 1.9.18, there is a Denial-of-service (crash) during block processing. This is fixed in 1.9.18.
CVE-2020-26240
PUBLISHED: 2020-11-25
Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. An ethash mining DAG generation flaw in Geth before version 1.9.24 could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on...