Skip to content
Sign in

Bug bounty program

UB

Uber

Open on HackerOneAtlas
Platform
HackerOne
Bounties
Pays
Assets in scope
4
Disclosed reports
239
Subdomains
11,395

Most upvoted reports239

All reports
Most upvoted reports of Uber
ReportWeaknessDisclosedBountyVotes
Sensitive user information disclosure at bonjour.uber.com/marketplace/_rpc via the 'userUuid' parameterAnalysed#542340Information Disclosure2019-09-09–643
[Pre-Submission][H1-4420-2019] API access to Phabricator on code.uberinternal.com from leaked certificate in git repoAnalysed#591813Information Disclosure2021-02-25$40,000458
Chained Bugs to Leak Victim's Uber's FB Oauth TokenAnalysed#202781Authentication2019-01-25–427
Reflected XSS and sensitive data exposure, including payment details, on lioncityrentals.com.sgAnalysed#340431Cryptography2020-04-30$4,000376
RCE via npm misconfig -- installing internal libraries from the public registryAnalysed#1007014Command and Code Injection2021-02-24$9,000325
Change any Uber user's password through /rt/users/passwordless-signup - Account Takeover (critical)Analysed#143717Authentication2016-07-14–312
XSS At "pages.et.uber.com"#156098Cross-site Scripting2016-08-19–267
Stored XSS in developer.uber.comAnalysed#131450Cross-site Scripting2016-06-27$7,500223
Unauthorized access to █████████.com allows access to Uber Brazil tax documents and system.Analysed#530441Access Control2021-03-06$4,500210
Authentication bypass on auth.uber.com via subdomain takeover of saostatic.uber.comAnalysed#219205Authentication2017-07-13–183

Subdomains11,395

Root
Scope
Name suggests:Data and files
First seen
Text fileClear filters37 names
Subdomains of Uber
NameScopeFirst seen
upload.auth.uber.comauth, dataNot in the scope2026-11-14
backup.uber.comdataNot in the scope2026-11-14
files.bonjour.uber.comdataNot in the scope2026-11-14
ftp.bonjour.uber.comdataNot in the scope2026-11-14
upload.bonjour.uber.comdataNot in the scope2026-11-14
s3.business.uber.comdataNot in the scope2026-11-14
upload.cn-neg-geo.cfe.uber.comdataNot in the scope2026-11-14
carrots-db-improvement.dev.uber.comdata, devNot in the scope2026-11-14
db-box.dev.uber.comdata, devNot in the scope2026-11-14
hqin-s3.dev.uber.comdata, devNot in the scope2026-11-14
jins-backup.dev.uber.comdata, devNot in the scope2026-11-14
jmishra-backup.dev.uber.comdata, devNot in the scope2026-11-14
kafka-spraynozzle-deb-packaging.dev.uber.comdata, devNot in the scope2026-11-14
kafka-yo-kafka.dev.uber.comdata, devNot in the scope2026-11-14
redis-grr.dev.uber.comdata, devNot in the scope2026-11-14
share-yo-kafka.dev.uber.comdata, devNot in the scope2026-11-14
files.uber.comdataNot in the scope2026-11-14
s3.frontends-cloudflare.uber.comdataNot in the scope2026-11-14
upload.help.uber.comdataNot in the scope2026-11-14
innovation-image-upload.uber.comdataNot in the scope2026-11-14
innovation-image-upload-staging.uber.comdata, stagingNot in the scope2026-11-14
files.driver.ios.mobile-config.uber.comdataNot in the scope2026-11-14
ftp.eats.ios.mobile-config.uber.comdataNot in the scope2026-11-14
mongo1.uber.comdataNot in the scope2026-11-14
mongo2.uber.comdataNot in the scope2026-11-14
mongo3.uber.comdataNot in the scope2026-11-14
mysql1.uber.comdataNot in the scope2026-11-14
mysql2.uber.comdataNot in the scope2026-11-14
mysql3.uber.comdataNot in the scope2026-11-14
db-spares-base22-dca1.prod.uber.comdataNot in the scope2026-11-14
sftp-frontend02-sjc1.prod.uber.comdataNot in the scope2026-11-14
s3.uber.comdataNot in the scope2026-11-14
sftp.uber.comdataNot in the scope2026-11-14
sftp-dca.uber.comdataNot in the scope2026-11-14
sftp-phx.uber.comdataNot in the scope2026-11-14
sftp-phx3.uber.comdataNot in the scope2026-11-14
sftp-sjc1.uber.comdataNot in the scope2026-11-14

0 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-14.

CyberSIXTSignal over noise
Updated AboutDevelopersSign in