Skip to content

Bug bounty reports15,219

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

Program:HackerOne
Status
Severity
Weakness
Year:2016
Clear
Bounty paid1
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed:No account
Technique
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Web Authentication Endpoint Credentials Brute-Force VulnerabilityAnalysed#127844ValidAuthentication–2016-06-23–161
Hacker.One Subdomain TakeoverAnalysed#159156ValidMisconfiguration and Insecure DesignLow2016-09-20–154
Bypass rate limiting on /users/password (possibly site-wide rate limit bypass?)Analysed#170310ValidMisconfiguration and Insecure DesignNone2016-12-08–76
(HackerOne SSO-SAML) Login CSRF, Open Redirect, and Self-XSS Possible ExploitationAnalysed#171398ValidCross-site ScriptingLow2016-10-27–44
Information leakage of private programAnalysed#159526ValidInformation Disclosure–2016-08-18$50035
Non-secure requests are not automatically upgraded to HTTPSAnalysed#158186ValidNo weakness recorded–2016-08-19–30
Interstitial redirect bypass / open redirect in https://hackerone.com/zendesk_sessionAnalysed#111968ValidOpen Redirect–2016-02-24–28
Know undisclosed Bounty Amount when Bounty Statistics are enabled.Analysed#148050ValidInformation Disclosure–2016-09-02–23

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