Intel · bug bounty
Disclosed bug bounty reports
Every publicly disclosed report on HackerOne the Atlas holds: HackerOne's own outcome, severity, the weakness as filed and the access the title states, and, for analysed reports, how the bug was found in our words.
SortMost upvoted
5 of 15,219 reports · $49,000 in bounties · 227 analysed so far
- #542340ValidAnalysedSensitive user information disclosure at bonjour.uber.com/marketplace/_rpc via the 'userUuid' parameterUber · Information Disclosure · 2019 · needs: no account · Missing authorisation check, IDOR / object reference, Leaked secret or key–643votes
- #591813ValidAnalysed[Pre-Submission][H1-4420-2019] API access to Phabricator on code.uberinternal.com from leaked certificate in git repoUber · Information Disclosure · 2021 · needs: no account · Leaked secret or key$40,000458votes
- #202781ValidAnalysedChained Bugs to Leak Victim's Uber's FB Oauth TokenUber · Authentication · 2019 · needs: no account · OAuth redirect_uri abuse, Account takeover chain–427votes
- #1007014ValidAnalysedRCE via npm misconfig -- installing internal libraries from the public registryUber · Command and Code Injection · 2021 · needs: no account · Dependency confusion / supply chain, Code injection / eval$9,000325votes
- #143717ValidAnalysedChange any Uber user's password through /rt/users/passwordless-signup - Account Takeover (critical)Uber · Authentication · 2016 · needs: no account · Authentication bypass, Account takeover chain, Password reset flaw–312votes
The status is HackerOne's own outcome. “Access (title)” is what the report's title states; “Access (analysis)” and techniques come from CyberSIXT's own analysis, a model's summary of the public report that may be wrong. Data as of 2026-11-14.