Responsible Disclosure

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

If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.

Please do the following:

  • E-mail your findings to [email protected]. Encrypt your findings using our PGP key to prevent this critical information from falling into the wrong hands,

  • Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data,

  • Do not reveal the problem to others until it has been resolved,

  • Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties, and

  • Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.

What we promise:

  • We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date,

  • If you have followed the instructions above, we will not take any legal action against you in regard to the report,

  • We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,

  • We will keep you informed of the progress towards resolving the problem,

  • In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise), and

  • As a token of our gratitude for your assistance, we offer a reward for every report of a security problem that was not yet known to us. The amount of the reward will be determined based on the severity of the leak and the quality of the report. Regarding severity, we consider (1) attack scenario / exploitability, and (2) security impact of the bug. Missing best practices without a real-life attack scenario are out of scope.

We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved.

This Coordinated Vulnerability Disclosure policy is based on an example written by Floor Terra on responsibledisclosure.nl.

At JOINSON&SPICE, we take cybersecurity seriously. The responsible disclosure of potential issues helps us ensure the security and privacy of our customers and their data.



Scope

We have listed the assets in scope for this program, however, if you have found a potential vulnerability (excluding the out of scope vulnerabilities listed below) on any product, system or asset you believe belongs to JOINSON&SPICE, please submit it through this program as we would like to hear about it.

  • *.joinsonandspice.nl

  • *.joinsonandspice.com

Please also note that JOINSON&SPICE employs third party vendors and some subdomains may be managed by third parties. Security issues found in third-party assets which are not managed by JOINSON&SPICE are considered out of scope and should be reported to the affected party directly. Please be sure to check our publicly published IP ranges and conduct all necessary due diligence to determine ownership of an asset prior to testing.

Out of Scope Vulnerabilities

While we value all vulnerabilities with real impact/exploitability, certain vulnerabilities are considered out of scope for our Responsible Disclosure Program. Out-of-scope vulnerabilities include:

  • Physical testing

  • Social engineering or phishing

  • Denial of service attacks

  • Resource Exhaustion Attacks

  • Clickjacking on pages with no sensitive actions

  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

  • Attacks requiring MITM or physical access to a user's device.

  • Previously known vulnerable libraries without a working Proof of Concept.

  • Missing best practices in SSL/TLS configuration.

  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

  • Missing HttpOnly or Secure flags on non-sensitive cookies

  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).

  • Open redirect - unless an additional security impact can be demonstrated

  • Issues that require unlikely user interaction