Responsible disclosure

1. Rules

   1. Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be triaged.
   2. Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
   3. Social engineering (e.g. phishing, vishing, smishing) is prohibited.
   4. Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

2. Scope

   At VanMoof, we consider the security of our systems – and our users – a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.

3. Out of Scope Vulnerabilities

   1. Clickjacking on pages with no sensitive actions.
   2. Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions.
   3. Attacks requiring MITM or physical access to a user's device.
   4. Previously known vulnerable libraries without a working Proof of Concept.
   5. Comma Separated Values (CSV) injection without demonstrating a vulnerability.
   6. Missing best practices in SSL/TLS configuration.
   7. Any activity that could lead to the disruption of our service (DoS).
   8. Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
   9. Rate limiting or bruteforce issues on non-authentication endpoints.
   10. Missing best practices in Content Security Policy.
   11. Missing HttpOnly or Secure flags on cookies.
   12. Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
   13. Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version].
   14. Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
   15. Tabnabbing
   16. Open redirect - unless an additional security impact can be demonstrated.
   17. In-store security or physical facilities.
   18. Third-party applications we make use of, but do not control. (e.g. a blog hosted on an external service - unless we've configured the blog in such a way as to make our in-scope areas vulnerable).
   19. Spam (unless a specific vulnerability leads to easily sending spam).
   20. Policies as opposed to implementations - email verification, password length or reuse, etc..
   21. Vulnerabilities in our open source software (unless you have a proof of concept of how the specific vulnerability can be used on vanmoof.com or related apps).
   22. Vulnerabilities that require access to an already compromised account (unless access to an account exposes other accounts).

4. How to submit a report

   1. If you discover something, please let us know immediately.
   2. Email your findings as quickly as possible to security ('at'sign) vanmoof (full stop) com.
   3. In the body of your email, please remember to tell us how you discovered the problem, so that we are able to reproduce it. Describe the problem and pass on the IP address or URL.
   4. Also include your contact information, such as an email address or telephone number. So that we can ask follow-up questions if applicable.

5. Safe Harbor

   Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy. Thank you for helping keep VanMoof and our users safe!

View as PDF