Better invites you to test and help secure our primary publicly facing assets - focusing on our web and api applications. We appreciate your efforts and hard work in making the internet (and Better) more secure, and look forward to working with the researcher community to create a meaningful and successful bug bounty program. Good luck and happy hunting!
For the initial prioritization/rating of findings, this program will use the Bugcrowd Vulnerability Rating Taxonomy. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.
Reward RangeLast updated
|Technical severity||Reward range|
|p1 Critical||$1,200 - $1,500|
|p2 Severe||$800 - $1,000|
|p3 Moderate||$300 - $500|
|p4 Low||$100 - $150|
Testing is only authorized on the targets listed as In-Scope. Any domain/property of Better not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you believe you've identified a vulnerability on a system outside the scope, please reach out to email@example.com before submitting.
*.better.com- The landing page for all of Better's services. Researchers are invited to test the entirety of this domain, including any and all subdomains.
api.better.com- One of the API endpoints utilized by Better's applications.
better.com/api- The other API endpoint utilized by Better's applications.
- Please sign up for an account using your @bugcrowdninja.com email address. For more info regarding @bugcrowdninja email addresses, see here.
- Submissions that chain multiple vulnerabilities may be eligible for a reward bonus.
Please do not include any Personally identifiable information (PII) in your reports, if you come across this information during the course of testing.
- Any reports about rate limiting (or lack of rate limiting) are out of scope.
Common low threats (i.e. information gathering or not exploitable on its own) are exempted. That being said, if you are able to demonstrate an exploit that utilizes low threats in combination with others, it is eligible.
- Descriptive error messages (e.g. Stack Traces, application or server errors).
- Clickjacking and issues only exploitable through clickjacking.
- Lack of Secure and HTTPOnly cookie flags.
- Weak Captcha / Captcha Bypass (captcha implementation issue)
- Username enumeration via Login Page error message
- Username enumeration via Forgot Password error message
- Login or Forgot Password page brute force and account lockout not enforced.
- SSL Attacks such as BEAST, BREACH, Renegotiation attack
- Missing HTTP security headers
When conducting vulnerability research according to this policy, we consider this research to be:
- Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
- Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls;
- Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
- You are expected, as always, to comply with all applicable laws.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through this program, or inquire via firstname.lastname@example.org before going any further.