Skip to content

Bug bounty reports15,219

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

Program:Slack
Status
Severity
Weakness:File and Path Handling
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 filters2 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Tricking the "Create snippet" feature into displaying the wrong filetype can lead to RCE on Slack users#833080ValidFile and Path Handling–2020-06-30$1,500101
[Android] Directory traversal leading to disclosure of auth tokens#1378889ValidFile and Path Handling–2022-02-25$3,50050

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

Updated AboutDevelopersSign in