Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:Slack
Status
Severity
Weakness:Open Redirect
Clear
Year
Bounty paid2
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters7 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Facebook Takeover using Slack using 302 from files.slack.com with access_token#6017ValidOpen Redirect–2015-01-11–17
Open redirect vulnerability#2731InformativeOpen Redirect–2014-04-06–11
Open Redirect login account#16718ValidOpen Redirect–2014-08-25$1008
URL redirection flaw#2622ValidOpen Redirect–2014-08-30–5
Trick make all fixed open redirect links vulnerable again#104087ValidOpen Redirect–2016-05-22$1,0004
open redirect in https://slack.com#6035InformativeOpen Redirect–2014-05-31–2
Open Redirect in Slack#4549InformativeOpen Redirect–2014-05-21–2

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 (4,365 analysed so far), which can be wrong. Data as of 2026-11-15.