Attacks/Breaches

4/12/2018
01:20 PM
50%
50%

Uber Agrees to New FTC Settlement Over 2016 Breach Disclosure

Uber has agreed to an updated settlement with the FTC after news of its massive 2016 data breach.

Uber has agreed to an expanded settlement with the Federal Trade Commission, which last year charged the ride-sharing company for deceiving customers with its privacy and data security practices. The new settlement takes into account Uber's massive 2016 data breach.

In the original settlement, proposed in August 2017, the FTC reported Uber failed to live up to claims that it closely monitored employees' access to rider and driver data, and that it implemented measures to secure personal data on third-party cloud servers.

The FTC later learned Uber had failed to disclose a significant breach of user data that occurred in 2016 while it was investigating this settlement. As a result, it has updated its complaint to note that Uber knew about the 2016 breach and paid the attackers $100,000 through a "bug bounty program" to keep quiet. The breach was disclosed a year after it occurred, in Nov. 2017.

In the new agreement, Uber is compelled to disclose future incidents involving consumer data and submit all reports from required third-party audits of its privacy program. It must retain certain records related to bug bounty reports of flaws that could compromise users' data. Uber could be subject to civil penalties if fails to share future incidents with the FTC.

Read more details here.

Interop ITX 2018

Join Dark Reading LIVE for two cybersecurity summits at Interop ITX. Learn from the industry’s most knowledgeable IT security experts. Check out the security track here. Register with Promo Code DR200 and save $200.

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
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Mueller Probe Yields Hacking Indictments for 12 Russian Military Officers
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/13/2018
10 Ways to Protect Protocols That Aren't DNS
Curtis Franklin Jr., Senior Editor at Dark Reading,  7/16/2018
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
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2016-10727
PUBLISHED: 2018-07-20
camel/providers/imapx/camel-imapx-server.c in the IMAPx component in GNOME evolution-data-server before 3.21.2 proceeds with cleartext data containing a password if the client wishes to use STARTTLS but the server will not use STARTTLS, which makes it easier for remote attackers to obtain sensitive ...
CVE-2018-8018
PUBLISHED: 2018-07-20
Apache Ignite 2.5 and earlier serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a spe...
CVE-2018-14415
PUBLISHED: 2018-07-20
An issue was discovered in idreamsoft iCMS before 7.0.10. XSS exists via the fourth and fifth input elements on the admincp.php?app=prop&do=add screen.
CVE-2018-14418
PUBLISHED: 2018-07-20
In Msvod Cms v10, SQL Injection exists via an images/lists?cid= URI.
CVE-2018-14419
PUBLISHED: 2018-07-20
MetInfo 6.0.0 allows XSS via a modified name of the navigation bar on the home page.