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:2020
Clear
Bounty paid4
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique
Clear filters6 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
duplicate hsts headers lead to firefox ignoring hsts on business.uber.comAnalysed#221955ValidNo weakness recordedLow2020-04-30$50027
Subdomain takeover on mta1a1.spmail.uber.comAnalysed#707748ValidAccess ControlMedium2020-04-06–30
Full Path and internal information disclosure+ SQLNet.log file disclose internal network informationAnalysed#410187ValidNo weakness recordedLow2020-04-23–34
Change the rating of any trip, therefore change the average driver ratingAnalysed#724522ValidInput Validation and LogicMedium2020-04-06$1,50043
ubernycmarketplace.com is vulnerable to the Heartbleed BugAnalysed#304190ValidInformation DisclosureLow2020-04-23$1,500112
Reflected XSS and sensitive data exposure, including payment details, on lioncityrentals.com.sgAnalysed#340431ValidCryptographyHigh2020-04-30$4,000376

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