By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Report Eligibility

Only reports that meet the following requirements are eligible to receive a monetary reward:

• You must be the first reporter of the vulnerability
• Sometimes, more than one researcher finds and reports the same issue while we are remediating. The bounty will not be split among duplicate reports.
• Issues found in alpha or beta products may be rewarded at lower levels due to much lower customer impact
• Issues that are the same root cause but are reported separately to describe attacks via different vectors may be treated as duplicate submissions.
• Reports that demonstrate a bypass of a mitigation for a security issue will be handled on a case-by-case basis
• Inquire about performing limited-scope targeted penetration tests if you have written a tool or found a technique to uncover the same issue on multiple endpoints, or different attack vectors or variants with the same root cause.
• The vulnerability must demonstrate security impact to a site or application in scope (see above)
• You must not have compromised the privacy of our users or otherwise violated the Dropbox Rules
• You must not have publicly disclosed the vulnerability prior to the report being closed and permission to disclose granted by the Dropbox team
• We must not be legally prohibited from rewarding you
• When researching security issues, especially those which may compromise the privacy of others, you must use test accounts in order to respect our users’ privacy. Accessing private information of other users, performing actions that may negatively affect Dropbox users (e.g., spam, denial of service), or sending reports from automated tools without verifying them will immediately disqualify the report, and may result in additional steps being taken.

RCE reports should provide the following additional information:

• Timestamp
• IP Address
• Command and Control Infrastructure used
• Timeline

If the RCE was authenticated please also provide:

• Email address (Please make sure to use your intigriti.me email alias when registering an account)
• Session ID

You must comply with all applicable laws in connection with your participation in this program. You are also responsible for any applicable taxes associated with any reward you receive.

We may modify the terms of this program or terminate this program at any time. We won’t apply any changes we make to these program terms retroactively.

Validation times

We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.
Submissions validated outside of this may be awarded a $25 bonus.

This remains at the discretion of Dropbox to award.

Domains

• Any report that can demonstrate security impact to Dropbox assets and domains listed in the program.

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:

Program feedback link
Please note this form will be checked periodically and should not be used for submission or support queries.

Domains

• Any domain that is not listed in the Domains section, is out of scope for this program
• Any domain or application with a planned deprecation plan will not be in-scope for the bug bounty program

Dropbox Specific

• Any issues pertaining to third-party AI model abuse should be reported to the AI developer team, for example: https://openai.com/form/model-behavior-feedback
• Any leaked third-party AI API keys should be reported to the AI developer, for example: https://forms.gle/h8bQ5YKWzXb8FtrQ8
• Reports about verification tokens in ./well-known/ai-plugin.json
• Any permissions violations by members of the same organization or team for permissions such as https://help.dropbox.com/security/change-admin-rights or https://help.docsend.com/hc/en-us/articles/360000840594-User-Roles or https://faq.hellosign.com/hc/en-us/articles/360038983232-Reporting-in-the-Admin-Console or any other Dropbox technology not listed explicitly above
• Any session handling reports that do not prove session persistence after 24 hours (Sessions not being invalidated). Session tokens remain valid for 24 hours by design.
• Password reset token reuse unless it can be demonstrated to persist after one hour or after password reset.
• Any sensitive customer data that was uploaded erroneously by that customer
• Any EXIF related reports that contain images that are stored in the user’s storage location are considered out of scope as Dropbox chooses not to alter the user’s photos.
• Bypass of URL malware detection
• Vulnerabilities only affecting users of outdated or unpatched browsers and platforms
• Reports of broken hyperlinks from Dropbox blog posts, press releases, or support articles
• Hosting malware/arbitrary content on Dropbox and causing downloads
• XSS on dropboxusercontent.com is out of scope
• Use of a known-vulnerable library (without evidence of exploitability)
• Reports from automated tools or scans
• Reports of spam (i.e., any report involving ability to send emails without rate limits)
• Attacks that require attacker app to have the permission to overlay on top of our app (e.g., tapjacking)
• Presence of autocomplete attribute on web forms
• Reports of insecure SSL/TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner)
• Any report on bypassing our storage limits etc. is out of scope
• Any report about DLL hijacking without demonstrating how it gains new privileges is also out of scope
• We will only accept critical reports in blog.dropbox.com (e.g., RCE). Minor issues that can't impact Dropbox users are out of scope
• Ability to share links without verifying email
• Reflected File Download vulnerabilities or any vulnerabilities that let you start a download to the user's computer are out of scope
• IP/Port Scanning via Dropbox services unless you are able to hit private IPs or Dropbox servers
• Devices (iOS, android, desktop apps) not getting unlinked on password change
• Hyperlink injection or any link injection in emails we send
• Creating multiple accounts using the same email
• Phishing risk via Unicode/Punycode or RTLO issues
• Being able to upload files with wrong extension in chooser
• Editable GitHub wikis
• 3rd Party Integrations not owned by Dropbox (i.e. Intercom Chat feature)
• Demo sites and scripts (i.e. apidemos.hellosign.com)

Application

• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that can't be used to exploit other users
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no or low impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits or the non-existence of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact/unrealistic user interaction
• CSV Injection
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks aren't sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact

General

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Mobile

• Shared links leaked through the system clipboard
• Any URIs leaked because a malicious app has permission to view URIs opened
• The absence of certificate pinning
• Sensitive data in URLs/request bodies when protected by TLS
• Lack of obfuscation
• Path disclosure in the binary
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Runtime hacking exploits (exploits only possible in a jailbroken environment)
• API key leakage used for insensitive activities/actions

This program follows Intigriti's triage standards based on the proof of concept.

Where can we get credentials for the app?

Dash.ai for Business
Please email bugbounty@dropbox.com to request test credentials that will expire in 30 days if not extended.

Other In-Scope Assets
For all other business and professional test accounts, please sign up for the free trial period. Make sure to deactivate your own business test accounts prior to billing.