Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| DoS through cache poisoning using invalid HTTP parametersAnalysed#326639 | Valid | Denial of Service | Medium | 2018-05-02 | – | 24 |
| Bypass of request line length limit to DoS via cache poisoningAnalysed#350847 | Valid | Denial of Service | Medium | 2018-09-16 | – | 24 |
| Cache poisoning using NULL bytes and long URLsAnalysed#334709 | Valid | Memory Corruption | Medium | 2018-09-16 | – | 32 |
| Subdomain Takeover using blog.greenhouse.io pointing to HubspotAnalysed#38007 | Valid | Cross-site Scripting | – | 2015-02-26 | – | 34 |
| Debug information disclosure on oauth-redirector.services.greenhouse.ioAnalysed#315205 | Valid | Information Disclosure | Medium | 2020-02-29 | – | 34 |
| Open S3 Bucket Accessible by any Aws UserAnalysed#819278 | Valid | Access Control | Low | 2020-05-01 | $100 | 53 |
| Subdomain Takeover on demo.greenhouse.io pointing to unbouncepagesAnalysed#407355 | Valid | Input Validation and Logic | High | 2020-03-05 | – | 76 |
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 (4,365 analysed so far), which can be wrong. Data as of 2026-11-15.