Skip to content

Bug bounty reports15,219

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

Program:Slack
Status
Severity
Weakness:Information Disclosure
Clear
Year
Bounty paid5
Access stated
Access needed
  • No account7
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters11 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Email information leakage for certain addresses#169992ValidInformation Disclosure–2016-10-31$4005
Session Fixation disclosing email address#2582InformativeInformation Disclosure–2014-03-31–7
Email enumeration#2766InformativeInformation Disclosure–2014-04-02–8
Information Disclosure on stun.screenhero.com#175061ValidInformation DisclosureMedium2016-11-30$70014
Private application files can be uploaded to Slack via malicious uploaderAnalysed#375083ValidInformation DisclosureMedium2021-08-04$50038
Workspace configuration metadata disclosureAnalysed#864489ValidInformation DisclosureHigh2022-04-01–39
Slack-Corp Heroku application disclosing limited info about company membersAnalysed#966814ValidInformation DisclosureLow2020-12-09–39
Real Time Error Logs Through Debug InformationAnalysed#503283ValidInformation DisclosureHigh2019-04-11–100
SSRF via Office file thumbnailsAnalysed#671935ValidInformation DisclosureCritical2022-07-05$4,000109
Unauthenticated LFI revealing log informationAnalysed#272578ValidInformation DisclosureHigh2018-01-26–123
AWS bucket leading to iOS test build code and configuration exposureAnalysed#404822ValidInformation DisclosureCritical2019-02-23$1,500321

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