Attacks/Breaches

12/7/2017
10:31 AM
50%
50%

Uber Used $100K Bug Bounty to Pay, Silence Florida Hacker: Report

Uber also performed a forensic analysis of the man's computer to ensure he had deleted the stolen information, Reuters said.

Uber reportedly paid a 20-year-old Florida man behind its massive data breach $100,000 from its bug bounty program to keep mum about the cyberattack and to delete the stolen data.

A Reuters report quotes unnamed sources familiar with the breach event as saying that Uber paid the man in order to confirm his identity, and had him sign a nondisclosure agreement to prevent him from doing any further damage. Uber also performed a forensic investigation on the man's computer to ensure he had deleted the stolen information.

The man reportedly paid another individual to steal Uber credentials from GitHub, which ultimately led to the Uber systems breach. According to a source quoted in the Reuters report, the man was "living with his mom in a small home trying to help pay the bills."

Uber's use of a bug bounty for the payment was an unusual move: bug bounty payments normally range from $5,000 to $10,000.

See Reuters' full article 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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
12/7/2017 | 1:30:24 PM
Oh Really???? The data IS DELETED?
Hard drive - put in a safe deposit box.  Think about it.  Tiny mental morons at work at Uber.  Well, they can always go to Equifax.
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Lessons from My Strange Journey into InfoSec
Lysa Myers, Security Researcher, ESET,  7/12/2018
What's Cooking With Caleb Sima
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14339
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the MMSE dissector could go into an infinite loop. This was addressed in epan/proto.c by adding offset and length validation.
CVE-2018-14340
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, dissectors that support zlib decompression could crash. This was addressed in epan/tvbuff_zlib.c by rejecting negative lengths to avoid a buffer over-read.
CVE-2018-14341
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the DICOM dissector could go into a large or infinite loop. This was addressed in epan/dissectors/packet-dcm.c by preventing an offset overflow.
CVE-2018-14342
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the BGP protocol dissector could go into a large loop. This was addressed in epan/dissectors/packet-bgp.c by validating Path Attribute lengths.
CVE-2018-14343
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the ASN.1 BER dissector could crash. This was addressed in epan/dissectors/packet-ber.c by ensuring that length values do not exceed the maximum signed integer.