Skip to content

Bug bounty reports15,219

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

Program:Uber
Status
Severity
Weakness
Year:2019
Clear
Bounty paid1
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Sensitive user information disclosure at bonjour.uber.com/marketplace/_rpc via the 'userUuid' parameterAnalysed#542340ValidInformation DisclosureHigh2019-09-09–643
Chained Bugs to Leak Victim's Uber's FB Oauth TokenAnalysed#202781ValidAuthenticationHigh2019-01-25–427
Open Redirect on central.uber.com allows for account takeoverAnalysed#206591ValidAuthenticationHigh2019-01-25–144
Client secret, server tokens for developer applications returned by internal APIAnalysed#419655ValidInformation Disclosure–2019-02-08–125
Lack of proper paymentProfileUUID validation allows any number of free rides without any outstanding balanceAnalysed#574638ValidInput Validation and LogicMedium2019-07-18–82
Subdomain takeover at signup.uber.comAnalysed#197489ValidAccess ControlHigh2019-01-25–79
Reflected XSS POST method at partners.uber.comAnalysed#129582ValidCross-site ScriptingMedium2019-01-25$3,00031
IDOR in activateFuelCard id allows bulk lookup of driver uuidsAnalysed#254151ValidInsecure Direct Object ReferenceLow2019-01-25–28

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.