At Label305 we believe the safety of the software products we develop, as well as our own systems is of the utmost importance. But no matter how much effort we put into system security, there can still be vulnerabilities present.

If you have found a vulnerability in one of our own systems, please let us know so that we can take action as soon as possible. We would like to work with you, so we are able to protect our end users, our clients and our systems.

Have you found a vulnerability in one of the software products we develop for a client? Also then we would like to hear from you, so that we can get to work quickly. Unfortunately we cannot always speak for our client. Therefore, first check the responsible disclosure policy of the software product itself.

We strive to solve all problems as quickly as possible and we are happy to be involved with a possible publication about the problem after it has been solved.

Please do the following:

  • mail your findings to 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. The minimum reward will be a € 50,- gift certificate.

This text is based on a text written by Floor Terra (Creative Commons Attribution 3.0).



We have no rewards for trivial or unexploitable security problems. Below you will find a number of examples of known vulnerabilities and accepted risks for which we do not reward a bounty.

  • HTTP server response with a non-200 status code;
  • Fingerprinting and version banner disclosure;
  • Everything related to our use of Homerun at;
  • Publicly accessible files and folders with non-sensitive information—e.g. robots.txt;
  • Clickjacking and related vulnerabilities;
  • CSRF on logout function or on forms available without a session—e.g. a contact form;
  • Presence of 'auto-complete' or 'save password' feature support;
  • Lack of 'Secure' and 'HTTP Only' flags on non-sensitive cookies;
  • A weak CAPTCHA or CAPTCHA bypassing;
  • Brute force on 'forgot password' form or 'account lockout' not enforced;
  • Allowed HTTP requests with OPTIONS method;
  • Username or e-mail address enumeration with brute force attempts via login error messages or 'forgot password' error messages;
  • Lack of HTTP headers such as: Strict-Transport-Security, X-Frame-Options, X-XSS-Protection, X-Content-Type-Options, Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP;
  • SSL configuration weaknesses including: SSL attacks that cannot be exploited externally, lack of SSL 'Forward Secrecy' and supporting unsafe cipher suites;
  • The lack of HTTP Public Key Pinning (HPKP);
  • Incorrectly configured SPF, DKIM, DMARC records;
  • 'Host' header injection;
  • Content spoofing and text injection on pages with an error message;
  • Reporting old software versions without a proof-of-concept of a working exploit;
  • The leakage of information through metadata;
  • Missing DNSSEC;
  • Expired or inactive domain names;
  • Same Site Scripting or use of a localhost DNS record.