Cloud

4/27/2018
02:02 PM
50%
50%

'Don't Extort Us': Uber Clarifies its Bug Bounty Policy

Updated parameters should help avoid future extortion incidents.

Uber this week outlined more specific guidlelines for its bug bounty program in the wake of its 2016 data breach that demonstrated gaping holes in its vulnerability disclosure policy.

The ride-sharing company last fall revealed that it had paid two hackers $100,000 to destroy driver and rider data they had stolen from a cloud storage location, and that it had failed to disclose the breach for a year. Since then, the company has been working on retooling its bug bounty program to encourage proper disclosure.

The new policy states, in part: "Don't extort us. You should never illegally or in bad faith leverage the existence of a vulnerability or access to sensitive or confidential information, such as making extortionate demands or ransom requests or trying to shake us down. In other words, if you find a vulnerability, report it to us with no conditions attached."

Read more 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
Page 1 / 2   >   >>
homekitchenary
50%
50%
homekitchenary,
User Rank: Apprentice
5/2/2018 | 11:11:09 PM
Don't Export Us
It is healthy for the <a href="https://homekitchenary.com/">business</a> to strive. It will Help uber for the long run.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/30/2018 | 9:01:35 PM
Re: Don't extort us
@jeremy. This also struck me as quite odd.
jconerly
50%
50%
jconerly,
User Rank: Apprentice
4/30/2018 | 2:28:17 PM
Re: Don't extort us
I think it is more about making it easier to ethically go after malicous actors using the bounty program as their method to ask for a ransom.  Publicly viewable hall of fame entries will be more valueable to whitehats since it can be used as a line on a resume and blackhats don't care because the value of security bugs from selling/using/ransoming it will almost always be higher than a bounty anyway.
jeremy_wittkop
50%
50%
jeremy_wittkop,
User Rank: Author
4/30/2018 | 11:45:00 AM
Re: Don't extort us
Agreed. A bounty program insinuates there is compensation for privately disclosed vulnerabilities. I would argue that the bounty program is designed to attract white hats. If someone is extorting you, they're not participating in the bounty program, they are simply black hats who exploited your vulnerabilities. I'm a little confused about why a bounty program would have to clarify that it is not encouraging people to commit a crime.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/29/2018 | 6:10:30 PM
Re: Paid two hackers $100,000
There are no guarantees and thats why it is bad practice to pay the ransom. I agree. The act of hacking in itself is not trustworthy, so never pay them, that would only make things worse.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/29/2018 | 6:08:46 PM
Re: Paid two hackers $100,000
No matter what, you should disclose and follow the correct security protocols. I agree, and never pay hackers and trust them, that is not what they are about.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/29/2018 | 6:07:11 PM
Re: Don't extort us
Don't Extort Us It may kot apeal most people, it say Do not a smart person would know that would result in an anti-reflection.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/29/2018 | 6:04:49 PM
Re: Don't extort us
Is there compensation for their bug bounty program? Most offer incentive to help ensure that their exposures are not publicly disclosed. I agree, I was just mentioning this in the other post.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
4/29/2018 | 6:03:41 PM
bug bounty program
The bug bounty program works best when there is a compansation, nobody would care otherwise.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/28/2018 | 7:51:06 PM
Paid two hackers $100,000
Many of the employees at the executive level paid dearly for this debacle. No matter what, you should disclose and follow the correct security protocols. Even if you take a hit towards brand reputation inititially, you will typically see that impact as much more detrimental if it is found that you tried to sweep it under the rug...

Also, who in their right mind trusts malcious actors to do the right thing? There are no guarantees and thats why it is bad practice to pay the ransom.
Page 1 / 2   >   >>
More Than Half of Users Reuse Passwords
Curtis Franklin Jr., Senior Editor at Dark Reading,  5/24/2018
Is Threat Intelligence Garbage?
Chris McDaniels, Chief Information Security Officer of Mosaic451,  5/23/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
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11506
PUBLISHED: 2018-05-28
The sr_do_ioctl function in drivers/scsi/sr_ioctl.c in the Linux kernel through 4.16.12 allows local users to cause a denial of service (stack-based buffer overflow) or possibly have unspecified other impact because sense buffers have different sizes at the CDROM layer and the SCSI layer.
CVE-2018-11507
PUBLISHED: 2018-05-28
An issue was discovered in Free Lossless Image Format (FLIF) 0.3. An attacker can trigger a long loop in image_load_pnm in image/image-pnm.cpp.
CVE-2018-11505
PUBLISHED: 2018-05-26
The Werewolf Online application 0.8.8 for Android allows attackers to discover the Firebase token by reading logcat output.
CVE-2018-6409
PUBLISHED: 2018-05-26
An issue was discovered in Appnitro MachForm before 4.2.3. The module in charge of serving stored files gets the path from the database. Modifying the name of the file to serve on the corresponding ap_form table leads to a path traversal vulnerability via the download.php q parameter.
CVE-2018-6410
PUBLISHED: 2018-05-26
An issue was discovered in Appnitro MachForm before 4.2.3. There is a download.php SQL injection via the q parameter.