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.

Cloud

8/13/2019
12:20 PM
50%
50%

700K Guest Records Stolen in Choice Hotels Breach

Cybercriminals reportedly stole the information from an exposed MongoDB database on a third-party server.

Hotel franchisor Choice Hotels has confirmed a breach in which attackers stole 700,000 guest records from a publicly available MongoDB database without a password or any authentication.

The unsecured server, which the hotel chain says belonged to a third-party vendor, contained multiple databases holding more than 5.6 million records. Choice Hotels says most of this was "test data," including fields referring to reservation details, passwords, and payment cards. Most of the 700,000 compromised records were in a database of 2.4 million records labeled "privacy log" and located in the same MongoDB instance. Exposed consumer data included names, physical and email addresses, phone numbers, and consent statuses, Comparitech reports.

Security researcher Bob Diachenko found the database on July 2, shortly after it was indexed by search engine BinaryEdge, and worked with Comparitech to analyze it. A ransom note demanding 0.4 Bitcoin was already there, likely left by an automated script targeting publicly accessible MongoDB databases, he believes. Diachenko notified Choice Hotels following his discovery; the firm secured the database on July 2 and began an investigation on July 28.

Choice Hotels says it will not be collaborating with this vendor in the future, and it's taking a closer look at its vendor relationships to put additional controls in place. It also plans to implement a responsible disclosure program to learn of future security incidents.

Read more details 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
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tdsan
50%
50%
tdsan,
User Rank: Ninja
8/13/2019 | 4:22:56 PM
Re: And the circle goes round and round .....
I am with you buddy, it seems the "SAGA" continues, it seems that companies and people are not familiar with the technology so they are just putting it out there without having a third-party vendor validate their design/implementation.

He also stated that it was a test environment to give Choice a new tool to test out new functionality. If that was the case, then why wasn't the system put in an enclosed network that does not allow Internet access and encrypt the data using AES2048 bit encryption, even if they got the data it would not be any good to them (of course if they happen to get the keys, then that is another story).

Choice Hotels Bitcoin Reply

I am like you, "come on people", and why did they use live data (700,000 records were real-data). Why wasn't the data created in an artificial scripted manner (per another article, they said 5.6 million records were artificial, so it looks like a marketing coverup but oh well, same story, different day)?

Time of Breach

Also, look at the timeline when Diachenko identified the issue:
  • June 30: The exposed database was first indexed by search engine BinaryEdge.
  • July 2: Security researcher Bob Diachenko discovered the database and immediately notified Choice Hotels about the exposure. It already contained the ransom note. Choice Hotels says it unintentionally filtered the email so that it was not read.
  • July 2: Database access was secured.
  • July 28: Diachenko sent a second notification and Choice Hotels began its investigation of the incident.

All I can say is wow.

T

 

 
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
8/13/2019 | 1:07:31 PM
And the circle goes round and round .....
External individual discovered the breech - not internal staff.  No passwords - not locked down.  Oh and minimal exposure of data - exactly what most firms say.  Have we not heard this before and before?  Oh and discovered June  but not investigated until June 28????    
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/1/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Threat from the Internet--and What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15478
PUBLISHED: 2020-07-01
The Journal theme before 3.1.0 for OpenCart allows exposure of sensitive data via SQL errors.
CVE-2020-6261
PUBLISHED: 2020-07-01
SAP Solution Manager (Trace Analysis), version 7.20, allows an attacker to perform a log injection into the trace file, due to Incomplete XML Validation. The readability of the trace file is impaired.
CVE-2020-15471
PUBLISHED: 2020-07-01
In nDPI through 3.2, the packet parsing code is vulnerable to a heap-based buffer over-read in ndpi_parse_packet_line_info in lib/ndpi_main.c.
CVE-2020-15472
PUBLISHED: 2020-07-01
In nDPI through 3.2, the H.323 dissector is vulnerable to a heap-based buffer over-read in ndpi_search_h323 in lib/protocols/h323.c, as demonstrated by a payload packet length that is too short.
CVE-2020-15473
PUBLISHED: 2020-07-01
In nDPI through 3.2, the OpenVPN dissector is vulnerable to a heap-based buffer over-read in ndpi_search_openvpn in lib/protocols/openvpn.c.