Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Open Redirect in Slack#4549 | Informative | Open Redirect | – | 2014-05-21 | – | 2 |
| open redirect in https://slack.com#6035 | Informative | Open Redirect | – | 2014-05-31 | – | 2 |
| Trick make all fixed open redirect links vulnerable again#104087 | Valid | Open Redirect | – | 2016-05-22 | $1,000 | 4 |
| URL redirection flaw#2622 | Valid | Open Redirect | – | 2014-08-30 | – | 5 |
| Open Redirect login account#16718 | Valid | Open Redirect | – | 2014-08-25 | $100 | 8 |
| Open redirect vulnerability#2731 | Informative | Open Redirect | – | 2014-04-06 | – | 11 |
| Facebook Takeover using Slack using 302 from files.slack.com with access_token#6017 | Valid | Open Redirect | – | 2015-01-11 | – | 17 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (3,935 analysed so far), which can be wrong. Data as of 2026-11-15.