Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Mass account takeovers using HTTP Request Smuggling on https://slackb.com/ to steal session cookiesAnalysed#737140 | Valid | Injection and Smuggling | – | 2020-03-12 | – | 870 |
| XSS vulnerable parameter in a location hashAnalysed#146336 | Valid | Cross-site Scripting | – | 2019-10-16 | – | 455 |
| AWS bucket leading to iOS test build code and configuration exposureAnalysed#404822 | Valid | Information Disclosure | – | 2019-02-23 | $1,500 | 321 |
| Slack DTLS uses a private key that is in the public domain, which may lead to SRTP stream hijackAnalysed#531032 | Valid | Cryptography | – | 2020-03-12 | $2,000 | 170 |
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.