Skip to content

Bug bounty reports15,219

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

Program:Uber
Status
Severity
Weakness:Denial of Service
Clear
Year
Bounty paid1
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters7 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Authorization issue in Google G Suite allows DoS through HTTP redirect#191196ValidDenial of Service–2017-02-09–62
Cookie Bombing cause DOS - businesses.uber.com#847493ValidDenial of Service–2021-02-24–14
Thumbor misconfiguration at blogapi.uber.com can lead to DoS#787240ValidDenial of Service–2021-02-25$5006
Header Injection#143076InformativeDenial of Service–2016-07-08–4
Uber password reset link EMAIL FLOOD#126364DuplicateDenial of Service–2016-06-13–3
Pixel flood attack in https://riders.uber.com/profile#126826InformativeDenial of Service–2016-04-25–2
SMS Flood with Update Profile#126536DuplicateDenial of Service–2016-06-13–1

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

Updated AboutDevelopersSign in