rabbit inc. vulnerability disclosure policy

Last Updated: Jun, 18 2024

Introduction

rabbit inc. welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.

Systems in Scope

This policy applies to any digital assets owned, operated, or maintained by rabbit inc.

Out of Scope

This policy does not apply to assets or other equipment not owned by rabbit inc. or its licensors, and such assets and equipment are out-of-scope.

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Our Commitments

When working with us, according to this policy, you can expect us to:

  • Respond to your report promptly, and work with you to understand and validate your report;
  • Strive to keep you informed about the progress of a vulnerability as it is processed;
  • Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
  • Extend Safe Harbor for your vulnerability research that is related to this policy.

Our Expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

  • Play by the rules, including following this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
  • Report any vulnerability you’ve discovered promptly;
  • Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
  • Use only the Official Channels to discuss vulnerability information with us;
  • Provide us a reasonable amount of time (at least 180 days from the initial report) to resolve the issue before you disclose it publicly;
  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
  • Only use exploits to the extent necessary to confirm a vulnerability’s presence. Make every effort to avoid using exploits that would compromise or exfiltrate information (including personally identifiable information (PII)), establish persistent command line access, or pivot to other information systems;
  • Vulnerability and security researchers should take additional efforts to avoid using exploits or actions that would compromise or exfiltrate PII. If while conducting security and vulnerability research authorized by this policy, a researcher accesses or exfiltrates or thinks it might access or exfiltrate PII, the vulnerability should be reported to rabbit immediately prior to such access or exfiltration, if possible, and the researcher should take reasonable steps to prevent access or disclosure (or any further access or disclosure) of the information. Also, researchers reporting a vulnerability that implicates PII shall take care not to include in their report any PII that may have been accessed by the vulnerability;
  • If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a proof of concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as PII, personal healthcare information (PHI), credit card data, or proprietary information;
  • You should only interact with test accounts you own or with explicit permission from the account holder; and
  • Do not engage in extortion.

Official Channels

Please report security issues via , providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.

Reports may be submitted anonymously or researchers may choose to provide their contact information. It is helpful to provide contact information, as the need arises to contact researchers to clarify reported vulnerability information or other technical interchange. Please do not send any of your additional personally identifiable information (PII) beyond name and contact information when submitting a report.

Please know that rabbit does not presently maintain any kind of bug bounty program, but, if we commence such a program, we will announce it in this Policy. Thus, unless and until we expressly announce otherwise, reporters will not receive payment for submitting vulnerabilities and, by submitting a report, reporters waive any claims to compensation.

Report Details

  • Reports should provide a detailed technical description of the steps required to reproduce the vulnerability.
  • Reports should include a description of any non-public information that may be accessible as a result of the vulnerability.
  • Reports should include a description of any tools needed to identify or exploit the vulnerability.
  • Note that images or videos, e.g., screen captures, and other documents may be attached to reports, and, if so, note that it is helpful to give attachments illustrative names.
  • Reports may include proof-of-concept code that demonstrates exploitation of the vulnerability.

    • But scripts or exploit code should be embedded into non-executable file types. All common file types and archives (e.g. txt, csv) can be processed, but executable code or macro-enabled documents cannot be accepted in submissions.

Safe Harbor

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

  • Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
  • Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
  • Exempt from restrictions in our Terms of Use that is posted on our website or in other documents, policies, or procedures that we may post or otherwise communicate with you that might interfere with conducting security and vulnerability research, and we waive those restrictions on a limited basis;
  • 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 legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report to before going any further.

Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.

By submitting a report to us, researchers warrant that the report and any attachments do not violate the intellectual property rights of any third party, and the reporter grants us a non-exclusive, royalty-free, world-wide, perpetual license to use, reproduce, create derivative works, and publish the report and any attachments.