summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2019-05-04 23:58:11 +0200
committerDaniel Stenberg <daniel@haxx.se>2019-05-04 23:59:04 +0200
commit8332bdece6492abb1faddedc58065f722a7b93a8 (patch)
treeb204623f35794c3d9cf69a25f54d219b3bab0b3c
parentc86d635b66ee0bf769076cfb1c187ccac032d41a (diff)
downloadcurl-bagder/bounty-dropbox.tar.gz
BUG-BOUNTY.md: add the Dropbox "bonus" extra payout ability [ci skip]bagder/bounty-dropbox
-rw-r--r--docs/BUG-BOUNTY.md29
1 files changed, 24 insertions, 5 deletions
diff --git a/docs/BUG-BOUNTY.md b/docs/BUG-BOUNTY.md
index de6d53e2f..82ed74da2 100644
--- a/docs/BUG-BOUNTY.md
+++ b/docs/BUG-BOUNTY.md
@@ -28,12 +28,12 @@ We offer reward money *up to* a certain amount per severity. The curl security
team determines the severity of each reported flaw on a case by case basis and
the exact amount rewarded to the reporter is then decided.
-At the start of the program, the award amounts are:
+The award amounts are:
- Critical: 2,000 USD
- High: 1,500 USD
- Medium: 1,000 USD
- Low: 500 USD
+ Critical: 32,000 USD
+ High: 6,000 USD
+ Medium: 1,000 USD
+ Low: 500 USD
# Who is eligible for a reward?
@@ -88,3 +88,22 @@ In the event that the individual receiving a curl bug bounty needs to pay
taxes on the reward money, the responsibility lies with the receiver. The
curl project or its security team never actually receive any of this money,
hold the money, or pay out the money.
+
+## Bonus levels
+
+In cooperation with [Dropbox](https://www.dropbox.com) the curl bug bounty can
+offer the highest levels of rewards if the issue covers one of the interest
+areas of theirs - and only if the bug is graded *high* or *critical*. A
+non-exhaustive list of vulnerabilities Dropbox is interested in are:
+
+ - RCE
+ - URL parsing vulnerabilities with demonstrable security impact
+
+Dropbox would generally hand out rewards for critical vulnerabilities ranging
+from 12k-32k USD where RCE is on the upper end of the spectrum.
+
+URL parsing vulnerabilities with demonstrable security impact might include
+incorrectly determining the authority of a URL when a special character is
+inserted into the path of the URL (as a hypothetical). This type of
+vulnerability would likely yield 6k-12k unless further impact could be
+demonstrated.