Responsible disclosure

At Wikibase Solutions, we consider the security of our systems and software 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 in one of our systems or products (including open-source products), we would like to hear from you as soon as possible so we can take steps to address it. We would like to ask you to help us better protect our clients and our systems.

You are cordially invited to actively search our products in an offline, non-production environment for security vulnerabilities, and report your findings to us. Out of accountability to our customers, we do not want to call for hacking attempts on their infrastructure. However, we still want to hear from you if you find a security vulnerability in one of these systems, so we can adequately remedy it.

If you discover a security vulnerability, we ask you to:

E-mail your findings as soon as possible to security@wikibase.nl,
Do not take advantage of the vulnerability or problem you have discovered, for example by downloading or accessing more data than necessary to demonstrate the vulnerability or by deleting or modifying other people's data,
Do not reveal the problem to anyone 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.

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

Clickjacking on pages with no sensitive actions;
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions;
Attacks requiring physical access to a user's device;
Previously known vulnerable libraries without a working proof of concept;
Missing best practices in SSL/TLS configuration;
Rate limiting or bruteforce issues on non-authentication endpoints;
Missing best practices in Content Security Policy;
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.);
Software version disclosure, banner identification issues, descriptive error messages or headers (e.g. stack traces, application or server errors).

You may optionally encrypt your report with PGP, using the following key (fingerprint: 37DB B4D2 B9DE 41AF 8752 6432 5F2C 19B1 B905 332F):

We promise that:

We will respond to your report within 5 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

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

We want to thank Fox-IT, Vodafone and ResponsibleDisclosure.nl for the example text.

Responsible disclosure

Contents

Address

Contact

Social

Information