Responsible Disclosure

At Openworx, 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 info@openworx.nl. 
  • 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.

Out of scope:

Below are examples of known or trivial vulnerabilities and accepted risks that fall outside the above regulation:

  • HTTP 404 codes/pages or other HTTP non-200 codes/pages and content spoofing/text injecting on these pages
  • Fingerprinting/version disclosure on public services
  • Public files or directories with non-sensitive information (e.g., robots.txt)
  • Clickjacking and issues that can only be exploited through clickjacking
  • Lack of secure/HTTP-only flags on non-sensitive cookies
  • OPTIONS HTTP method enabled
  • Rate limiting vulnerabilities without clear impact
  • Anything related to HTTP security headers, for example:
    • Strict-Transport-Security
    • X-Frame-Options
    • X-XSS-Protection
    • X-Content-Type-Options
    • Content-Security-Policy
  • SSL configuration issues
  • SSL Forward Secrecy disabled
  • Weak/insecure cipher suites
  • Issues with SPF, DKIM, or DMARC
  • Host header injection
  • Reporting outdated versions of any software without proof of concept of a working exploit
  • Information exposure in metadata
  • Demo environments

What we promise:

  • 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).

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.