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.

Vulnerabilities / Threats

9/27/2019
10:30 AM
50%
50%

DoorDash Breach Affects 4.9M Merchants, Customers, Workers

The May 4 incident exposed data belonging to users on the platform on or before April 5, 2018.

Food delivery service DoorDash this week confirmed a data breach exposing information belonging to 4.9 million consumers, merchants, and delivery workers on its platform.

DoorDash learned of "unusual activity involving a third-party service provider," which it did not specify, earlier this month. An investigation revealed an unauthorized party accessed some DoorDash data on May 4, 2019. While the company says it took "immediate steps" to block further access by the intruder, it's unclear why the breach took nearly five months to notice.

Those who joined the platform on or before April 5, 2018 are affected by the breach; those who joined after April 5, 2018 are not. DoorDash is reaching out to users whose data was exposed.

The type of user data compromised could include profile information such as names, email addresses, delivery addresses, order history, phone numbers, and hashed, salted passwords. Attackers may have also obtained the last four digits of some consumers' payment cards; however, DoorDash emphasizes full payment card numbers and CVVs were not accessed.

For some merchants and delivery workers, or "Dashers," the last four digits of bank account numbers were compromised. Full bank account information was not. Approximately 100,000 Dashers also had their driver's license numbers compromised in the breach.

DoorDash reports it has added security measures around its data, improved security protocols that grant access to its systems, and hired outside security experts for better threat detection.

Read more details here.

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Why Clouds Keep Leaking Data"

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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18986
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 allow attackers to brute-force (guess) valid usernames by using the 'forgot password' functionality as it returns distinct messages for invalid password and non-existing users.
CVE-2019-18981
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 lacks an Access Denied outcome for a certain scenario of an incorrect recipient ID of a notification.
CVE-2019-18982
PUBLISHED: 2019-11-15
bundles/AdminBundle/Controller/Admin/EmailController.php in Pimcore before 6.3.0 allows script execution in the Email Log preview window because of the lack of a Content-Security-Policy header.
CVE-2019-18985
PUBLISHED: 2019-11-15
Pimcore before 6.2.2 lacks brute force protection for the 2FA token.
CVE-2019-18928
PUBLISHED: 2019-11-15
Cyrus IMAP 2.5.x before 2.5.14 and 3.x before 3.0.12 allows privilege escalation because an HTTP request may be interpreted in the authentication context of an unrelated previous request that arrived over the same connection.