Rainforest QA Responsible Vulnerability Disclosure Policy
Rainforest recognizes the importance of security researchers in helping keep our customers safe. We encourage responsible disclosure of security vulnerabilities as described on this page.
Responsible disclosure includes:
- Providing us a reasonable amount of time to fix the issue before publishing it elsewhere.
- Making a good faith effort to not leak or destroy any Rainforest user data.
- Not defrauding Rainforest users or Rainforest itself in the process of discovery.
- In order to encourage responsible disclosure, we promise not to bring legal action against researchers who point out a problem provided they do their best to follow the above guidelines.
Attribution on our Hall of Fame hosted in this page.
Monetary compensation is not currently offered under this program.
Rainforest reserves the right to decide if the minimum severity threshold has been met and whether it was previously reported.
In general, anything which has the potential for financial loss or data breach is of sufficient severity, including:
- Authentication bypass or privilege escalation
- Click jacking (except on www.rainforestqa.com)
- Remote code execution
- Obtaining user information
In general, the following would not meet the threshold for severity:
- Vulnerabilities on sites hosted by third parties (blog.rainforest.com, analytics, info.rainforestqa.com, status.rainforestqa.com, etc) unless they lead to a vulnerability on the main website
- Denial of Service and brute-force attacks
- Non-ideal but non-exploitable configuration issues
- Spamming or phishing
- Vulnerabilities in third party applications, such as Stripe or Heroku
- Vulnerabilities in third party applications which make use of the Rainforest API
- Clickjacking on the marketing website (www.rainforestqa.com)
For example, “Your servers are vulnerable to Heartbleed” (with reasonable proof) will absolutely get you a reward, but “Your servers don’t get an A+ rating on SSL Labs” will definitely not. Don’t expect a response for any reported issues that don’t fit with the guidelines.
How To Disclose
Please include if possible:
- Description and potential impact
- Steps to reproduce the issue or a proof of concept
- Name and link for attribution on this page
- Thank you for helping keep our community safe!
Hall of Fame
- 2nd October 2017 — Yeasir Arafat
- 22th September 2017 — Prial Islam
- 6th July 2017 — Shubham Pathak
- 20th June 2017 — Maulik Vaidh