Vulnerability Disclosure Policy
We take the safety of our customers data very seriously. If you believe you’ve discovered a potential vulnerability within one of our services or products, we strongly encourage you disclose it to us as quickly as possible and in a responsible manner.
We appreciate the assistance and patience of researchers and are committed to reviewing all issues that are disclosed to us. We will do our best to address each issue in a timely fashion, and request that you provide us with a reasonable timeframe to address the issue before public disclosure.
Please do not publicly disclose the details of any potential vulnerabilities without express written consent from us.
The following types of research are strictly prohibited:
- Accessing or attempting to access accounts or data that does not belong to you
- Testing third party websites, plug-ins, applications or services that integrate with our services or products
- Any attempt to modify or destroy any data
- Executing or attempting to execute a denial of service (DoS) attack
- Sending or attempting to send unsolicited or unauthorised email, spam or any other form of unsolicited messages
- Conducting social engineering (including phishing) of Crewmojo employees, contractors or customers or any other party
- Any physical attempts against our property or data centres, including (but not limited to) distribution facilities, offices
- Posting, transmitting, uploading, linking to, sending or storing malware, viruses or similar harmful software that could impact our services, products or customers or any other party
- Any activity that violates any law
The following vulnerability types are excluded from this Responsible Disclosure Program:
- Descriptive error messages such as stack traces, application or server errors
- HTTP 404 codes or pages, or other HTTP non-200 codes or pages
- Fingerprinting or banner disclosure on common and public services
- Disclosure of known public files or directories, such as robots.txt
- Clickjacking and other issues only exploitable through clickjacking
- CSRF on forms that are available to anonymous users, such as contact, login and logout forms
- Content spoofing
- Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality
- Lack of Secure or HTTPOnly flags on non-sensitive cookies
- Login or Forgot Password page brute force and account lockout not enforced
- OPTIONS HTTP method enabled
- Missing HTTP security headers, such as Strict Transport Security, X-Frame-Options, X-SSS-Protection, etc.
- HTTP or DNS cache poisoning
- Weak or insecure SSL cipher suites
To encourage responsible disclosure, we will not take legal action against researchers in relation to the discovery and reporting of a potential vulnerability. This is provided that all such potential vulnerabilities are discovered and reported strictly in accordance with this policy. In the event of any non-compliance, we reserve all of our legal rights.
If in doubt, please contact the Crewmojo by sending an email to email@example.com.
Communication Process - How to Report a Potential Vulnerability
You can responsibly disclose potential vulnerabilities to Crewmojo through our Disclosure Platform
or by emailing firstname.lastname@example.org. Ensure that you include details of the potential vulnerability and exploit with enough information to enable Crewmojo to reproduce your steps.
- An explanation of the potential vulnerability;
- A list of products and services that may be affected (where possible);
- Steps to reproduce the vulnerability;
- Proof-of-concept code (where applicable);
- The names of any test accounts you have created (where applicable); and
- Your contact information.
What happens next?
Once you have reported a potential vulnerability, we will contact you within 72 hours with an initial response. Going forward, we will keep you informed on our progress towards addressing the potential vulnerability and will also notify you when the matter has been addressed.
We ask that you maintain confidentiality and do not make your research public until we have completed our investigation and, if necessary, remediated or mitigated the potential vulnerability.
Please note that we do not compensate individuals or organisations for identifying potential or confirmed vulnerabilities. Any requests for any compensation will be deemed in violation of this Responsible Disclosure Program.