-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit 4509f8f
Showing
2 changed files
with
151 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| # Contributors | ||
|
|
||
| Chris Evans' work on the [Dropbox VDP](https://blogs.dropbox.com/tech/2018/03/protecting-security-researchers) both inspired us and provided a starting point to work from. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,148 @@ | ||
| <h1>Vulnerability Disclosure Policy</h1> | ||
| <p>Keeping user information safe and secure is of the utmost importance and a core company value, and we can't feasibly accomplish that without the help of external security researchers. Consequently, we have formalized a vulnerability disclosure policy and reward program in order to be able to show appreciation for their effort, skill and dedication.</p> | ||
| <h2>Rewards</h2> | ||
| <p>We provide rewards to vulnerability reporters at our discretion. In order to be eligible for a bounty, your submission must be accepted as valid.</p> | ||
| <p>We use the following guidelines to determine the validity of requests and the reward compensation offered.</p> | ||
| <h3><i>Reproducibility</i></h3> | ||
| <p>Our engineers must be able to reproduce the vulnerability you have reported. Reports that include clearly written explanations and a working proof of concept are more likely to receive awards.</p> | ||
| <h3><i>Severity and Priority</i></h3> | ||
| <p>Our focuses for security research are listed as 'in-scope' with their priority indicated. More impactful bugs will be receive larger awards.</p> | ||
| <h3><i>Rewards</i></h3> | ||
| <p>Reward amounts may vary depending upon the severity of the vulnerability reported and quality of the report. If we receive multiple reports of the same vulnerability, the first clear, reproducible report will be rewarded.</p> | ||
| <p>Below is a chart showing typical rewards for vulnerabilities that are within scope:</p> | ||
|
|
||
| <table class='table-vuln-level-rewards'> | ||
| <tbody> | ||
| <tr> | ||
| <th><strong>Vulnerability Level</strong></th> | ||
| <th><strong>Reward</strong></th> | ||
| </tr> | ||
| <tr> | ||
| <td>Critical</td> | ||
| <td>$1,500</td> | ||
| </tr> | ||
| <tr> | ||
| <td>High</td> | ||
| <td>$900</td> | ||
| </tr> | ||
| <tr> | ||
| <td>Medium</td> | ||
| <td>$300</td> | ||
| </tr> | ||
| <tr> | ||
| <td>Low</td> | ||
| <td>$100</td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| <p>Examples of Vulnerability Levels:</p> | ||
|
|
||
| <strong>Critical:</strong> | ||
|
|
||
| <ul> | ||
| <li>Remote code execution</li> | ||
| <li>SQL injection with significant impact</li> | ||
| <li>Vertical authentication bypass</li> | ||
| </ul> | ||
|
|
||
| <strong>High:</strong> | ||
|
|
||
| <ul> | ||
| <li>Lateral authentication bypass</li> | ||
| <li>Stored XSS with significant impact</li> | ||
| <li>CSRF with significant impact</li> | ||
| <li>Internal SSRF</li> | ||
| </ul> | ||
|
|
||
| <strong>Medium:</strong> | ||
|
|
||
| <ul> | ||
| <li>Reflective XSS with impact</li> | ||
| <li>Direct object reference</li> | ||
| <li>URL redirect</li> | ||
| <li>CSRF with impact</li> | ||
| </ul> | ||
|
|
||
| <strong>Low:</strong> | ||
|
|
||
| <ul> | ||
| <li>SSL misconfigurations with little impact</li> | ||
| <li>SPF configuration problems</li> | ||
| <li>XSS with limited impact</li> | ||
| <li>CSRF with limited impact</li> | ||
| </ul> | ||
|
|
||
| <p>We may decide to pay higher rewards for clever or severe vulnerabilities, decide to pay lower rewards for vulnerabilities that require unusual user interaction, decide that a single report constitutes multiple bugs, or that multiple reports are so closely related that they only warrant a single reward.</p> | ||
| <h2>Disclosure</h2> | ||
| <p>We would very much like to highlight the incredible work that external researchers do for us and one way we can do that is to publicly disclose vulnerabilities in a timely manner with proper attribution. To facilitate this, please:</p> | ||
| <ul> | ||
| <li>Share the security issue with us in detail</li> | ||
| <li>Give us a reasonable time to remediate the issue before making any information about it public.</li> | ||
| <li>When we have remediated the issue, remain in communication to coordinate public disclosure timelines.</li> | ||
| </ul> | ||
| <h2>Guidelines for investigating and reporting bugs</h2> | ||
| <ul> | ||
| <li>Be clear and succinct, a short proof-of-concept link is invaluable. Visit the Bug Hunter University articles to learn more about sending good vulnerability reports.</li> | ||
| <li>Be respectful of our existing applications. Respect their Terms of Service and avoid scanning techniques that are likely to cause degradation of service to other customers.</li> | ||
| <li>Do not access or modify our data or our users’ data, without explicit permission of the owner. Only interact with your own accounts or test accounts for security research purposes.</li> | ||
| <li>Contact us immediately if you do inadvertently encounter user data. Do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability.</li> | ||
| <li>Act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service).</li> | ||
| <li><strong>Otherwise comply with all applicable laws.</strong></li> | ||
| </ul> | ||
| <h2>In Scope</h2> | ||
| <p>The applications listed under 'in-scope' are explicitly eligible for the bounty program.</p> | ||
| <p>Any design or implementation issue that substantially affects the confidentiality or integrity of user data is likely to be in scope for the program. Common examples include:</p> | ||
| <ul> | ||
| <li>Cross-site scripting.</li> | ||
| <li>Cross-site request forgery.</li> | ||
| <li>Mixed-content scripts.</li> | ||
| <li>Authentication or authorization flaws.</li> | ||
| <li>Server-side code execution bugs.</li> | ||
| <li>Circumvention of our permissions model.</li> | ||
| <li>SQL injection.</li> | ||
| <li>XML external entity Attacks.</li> | ||
| </ul> | ||
| <p>While this list represents our primary focus for security research, we are interested in reports for all of our software and dependencies especially if when it impacts reasonably sensitive user data. This can include any open source libraries, software, or third-party components. At our discretion, we will issue rewards for reports not included in the in-scope list.</p> | ||
| <h2>Out of Scope</h2> | ||
| <p>The applications listed under 'out of scope' are explicitly ineligible. We will not disclose vulnerabilities reported regarding out of scope applications, nor will we issue rewards for them.</p> | ||
| <p>In addition, the following issues are outside of the scope of our rewards program:</p> | ||
| <ul> | ||
| <li>Policies on presence/absence of SPF/DMARC records.</li> | ||
| <li>Password, email and account policies, such as email id verification, reset link expiration, and password complexity.</li> | ||
| <li>Logout cross-site request forgery.</li> | ||
| <li>Attacks requiring physical access to a user's device.</li> | ||
| <li>XSS on any site other than those listed as 'in scope'.</li> | ||
| <li>Attacks that require attacker app to have the permission to overlay on top of our app (e.g., tapjacking).</li> | ||
| <li>Vulnerabilities that require a potential victim to install non-standard software or otherwise take active steps to make themselves be susceptible.</li> | ||
| <li>Vulnerabilities affecting users of outdated browsers or platforms.</li> | ||
| <li>Social engineering of our employees or contractors.</li> | ||
| <li>Any physical attempts against our property or data centers.</li> | ||
| <li>Presence of autocomplete attribute on web forms.</li> | ||
| <li>Missing cookie flags on non-sensitive cookies.</li> | ||
| <li>Any access to data where the targeted user needs to be operating a rooted mobile device.</li> | ||
| </ul> | ||
| <p>The following issues are outside the scope of our rewards program unless they are accompanied by evidence of exploitability:</p> | ||
| <ul> | ||
| <li>Use of a known-vulnerable library.</li> | ||
| <li>Missing best practices.</li> | ||
| <li>Insecure SSL/TLS ciphers.</li> | ||
| <li>Missing security headers which do not lead directly to a vulnerability.</li> | ||
| <li>Lack of CSRF tokens (unless there is evidence of actual, sensitive user action not protected by a token).</li> | ||
| <li>Host header injections.</li> | ||
| <li>Reports from automated tools or scans that haven't been manually validated.</li> | ||
| <li>Presence of banner or version information unless correlated with a vulnerable version.</li> | ||
| </ul> | ||
| <p>For more additional information about issues that are commonly out of scope, refer to Google Bughunter University.</p> | ||
| <h2>Known Issues</h2> | ||
| <p>Any issues already known to us which are in the process of being remediated will be published as a Known Issues list below. These vulnerabilities are considered out of scope, but additional reports of them may qualify for rewards if they are new instances which were not previously observed.</p> | ||
| <h2>Consequences of Complying with This Policy</h2> | ||
| <p>We will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy.</p> | ||
| <p>We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act.</p> | ||
| <p>To the extent your activities are inconsistent with certain restrictions in our Acceptable Use Policy, we waive those restrictions for the limited purpose of permitting security research under this policy.</p> | ||
| <p>We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.</p> | ||
| <p>If legal action is initiated by a third party against you and you have complied with this policy policy, we will take steps to make it known that your actions were conducted in compliance with this policy.</p> | ||
| <p>Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.</p> | ||
| <h2>The Fine Print</h2> | ||
| <p>This is not a competition, but rather an experimental and discretionary rewards program. We may modify the terms of this program, terminate this program at any time, or not pay a reward entirely at our discretion.</p> | ||
| <p>We won't apply any changes we make to these program terms retroactively. Reports from individuals who we are prohibited by law from paying are ineligible for rewards. You are responsible for paying any taxes associated with rewards. Any rewards that are unclaimed after 12 months will be donated to a charity of our choosing.</p> |