Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| TURN server allows TCP and UDP proxying to internal network, localhost and meta-data servicesAnalysed#333419 | Valid | Server-Side Request Forgery | Critical | 2020-03-12 | $3,500 | 323 |
| Header modification results in disclosure of Slack infra metadata to unauthorized partiesAnalysed#727330 | Valid | Server-Side Request Forgery | Medium | 2021-06-09 | – | 97 |
| SSRF in api.slack.com, using slash commands and bypassing the protections.Analysed#381129 | Valid | Server-Side Request Forgery | Medium | 2019-02-22 | – | 84 |
| Bypass of the SSRF protection in Event Subscriptions parameter.Analysed#386292 | Valid | Server-Side Request Forgery | Medium | 2019-02-22 | – | 52 |
| Internal SSRF bypass using slash commands at api.slack.comAnalysed#356765 | Valid | Server-Side Request Forgery | Medium | 2018-07-12 | – | 51 |
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.