BUG BOUNTY POLICY
Capitalized terms used in this Bug Bounty Policy and not otherwise defined have the meaning ascribed to such terms in our Terms of Service (https://www.outbound.io/tos).
Outbound aims to keep its Service safe for everyone, and data security is of utmost priority. If you are a security researcher and have discovered a security vulnerability in the Service, we appreciate your help in disclosing it to us privately and giving us an opportunity to fix it before publishing technical details.
Outbound will engage with security researchers when vulnerabilities are reported to us as described here. We will validate, respond, and fix vulnerabilities in support of our commitment to security and privacy. We won’t take legal action against, suspend, or terminate access to the Service of those who discover and report security vulnerabilities responsibly. Outbound reserves all of its legal rights in the event of any noncompliance.
Share the details of any suspected vulnerabilities with the Zendesk Security Team by filing a report (https://hackerone.com/outbound/reports/new). Please do not publicly disclose these details outside of this process without explicit permission. In reporting any suspected vulnerabilities, please include the following information:
* Vulnerable URL - the endpoint where the vulnerability occurs;
* Vulnerable Parameter - if applicable, the parameter where the vulnerability occurs;
* Vulnerability Type - the type of the vulnerability;
* Steps to Reproduce - step-by-step information on how to reproduce the issue
* Screenshots or Video - a demonstration of the attack; and
* Attack Scenario - an example attack scenario may help demonstrate the risk and get your issue resolved faster.
Reports that carry an acceptable risk but demonstrate a valid security-related behavior will be closed as informative. Submissions that don’t present a security risk, are false positives, or are out of scope will be closed as N/A. (Please note that the scope is outlined below.)
Identical reports will be marked as “Duplicate[s]” of the original submission; the original report can be marked as (but not limited) to “Triaged”, “N/A”, or “Informative.”
More information on a proper submission (https://support.hackerone.com/hc/en-us/articles/205072249-What-does-a-good-report-look-like-), report states (https://support.hackerone.com/hc/en-us/articles/205624695), and acceptable reporting behavior (https://support.hackerone.com/hc/en-us/articles/208475476-What-are-examples-of-bad-behavior-), can be found on linked Hackerone’s articles.
In no event are you permitted to access, download or modify data residing in any other Account, or one that is not registered to you.
You are also prohibited from:
* Executing or attempting to execute any Denial of Service attack.
* Knowingly posting, transmitting, uploading, linking to, sending or storing any Malicious Software.
* Attempting to social engineer support staff.
* Testing in a manner that would result in the sending of unsolicited or unauthorized junk mail, spam, pyramid schemes or other forms of duplicative or unsolicited messages.
* Testing in a manner that would degrade the operation of the Service.
* Testing or otherwise accessing or using the Service from any jurisdiction that is a Prohibited Jurisdiction.
* Testing third party applications or websites or services that integrate with or link to the Service.
Bounty Ineligible Issues
The following items are known issues or accepted risks where we will not reward you:
* Brute-force, / Rate-limiting, / Velocity throttling, and other denial of service based issues.
* Content spoofing issues without branding CSS.
* Cookie flags.
* Covert Redirects.
* Issue where the fix only requires a text change.
* Login/Logout CSRF
* Malicious attachments on file uploads or attachments.
* Missing additional security controls, such as HSTS or CSP headers
* Password recovery policies, such as reset link expiration or password complexity
* Reflected File Download (this may be rewarded in the future, but is currently out of scope)
* SPF, DKIM, DMARC issues.
* XSS (or a behavior) where you can only attack yourself
* XSS on pages where admins are intentionally given full HTML editing capabilities, such as custom theme editing
We are pleased to offer a bounty for vulnerability information that helps us protect our customers as a thanks to the security researchers who choose to participate in our bug bounty program. Outbound will decide the bounty amounts at our sole discretion, and all decisions are final.
We will reward you for the following types of vulnerabilities (except where noted otherwise in our Testing Exclusions and bounty ineligible section):
| Severity | Estimated Bounty | Example Issues |
| Critical | $1,000+ | Remote Code Execution, SQL Injection |
| High | $500+ | Significant Broken Authentication or Session Management, Stored XSS, CSRF and Privilege Escalation on critical functionality, etc. |
| Medium | $100+ | Access Control Bypass, Privilege Escalation, Reflective XSS, CSRF, Open URL Redirection, Directory Traversal, etc.
| Low | $50+ | Information Leakage, XSS or CSRF between Admins, Theoretical attacks, etc. |
We will only reward the first reporter of a valid vulnerability. Any duplicate reports will not be rewarded.
You are responsible for paying any taxes associated with the reward. Submissions from countries where we are prohibited by law from making payments, such as the US Sanction Lists (http://www.treasury.gov/resource-center/sanctions/Programs/Pages/Programs.aspx), are ineligible for rewards.
Any submissions received prior to the launch of this bug bounty (April 27th, 2015) are also ineligible for rewards.
If you identify a verified security vulnerability in compliance with this Bug Bounty Policy, Outbound commits to:
* Acknowledge receipt of your vulnerability report in a timely manner;
* Notify you when the vulnerability is fixed; and
* Publicly thank you (https://hackerone.com/outbound/thanks) for your responsible disclosure and helping us keep our customers safe.
You may test only against a Outbound Account for which you are the Account Owner or an Agent authorized by the Account Owner to conduct such testing. The following Outbound applications are in-scope:
Please use the syntax firstname.lastname@example.org and/or Hackerone as the company name during registration.
Hall of Fame