Skip to content

Bug bounty reports15,219

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

Program:Slack
Status
Severity
Weakness
Year:2019
Clear
Bounty paid4
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters11 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Invitation reminder emails contain insecure linksAnalysed#327674ValidCryptographyLow2019-06-29$35015
CSS Injection to disable app & potential message exfilAnalysed#679969ValidInput Validation and LogicMedium2019-11-09–37
Information leakage and default open portAnalysed#305518ValidNo weakness recordedLow2019-06-22–41
Linux Desktop application slack executable does not use pie / no ASLRAnalysed#415272ValidMisconfiguration and Insecure DesignLow2019-11-17$10047
Bypass of the SSRF protection in Event Subscriptions parameter.Analysed#386292ValidServer-Side Request ForgeryMedium2019-02-22–52
SSRF in api.slack.com, using slash commands and bypassing the protections.Analysed#381129ValidServer-Side Request ForgeryMedium2019-02-22–84
User-assisted RCE in Slack for macOS (from official site) due to improper quarantine meta-attribute handling for downloaded filesAnalysed#470637ValidNo weakness recordedHigh2019-09-14–97
Real Time Error Logs Through Debug InformationAnalysed#503283ValidInformation DisclosureHigh2019-04-11–100
XSS in gist integrationAnalysed#11073ValidCross-site Scripting–2019-04-28$500157
AWS bucket leading to iOS test build code and configuration exposureAnalysed#404822ValidInformation DisclosureCritical2019-02-23$1,500321
XSS vulnerable parameter in a location hashAnalysed#146336ValidCross-site Scripting–2019-10-16–455

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, where there is one, which can be wrong. Data as of 2026-11-15.