Vulnerability disclosure

At Cleverbase 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

  • Send your findings in via our Report a vulnerability form. This is the only channel for reporting a vulnerability.
  • 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.
  • 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.

Findings not submitted in accordance with the above procedure will not be considered.

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, unless we are legally required to do so. You may also submit your report under a pseudonym.
  • 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 do not run a bug bounty programme. As a token of our gratitude for your assistance, we publish the finding and your name as the reporter in our hall of fame, unless you prefer to remain anonymous.

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.

Scope

Our vulnerability disclosure procedure covers cleverbase.com and its subdomains, unless stated otherwise below. The following subjects are not in scope:

  • cleverbase.io and its subdomains.
  • acc.cleverbase.com and tst.cleverbase.com, and any subdomains beneath them.
  • Disclosure of publicly available software or source code.
  • HTTP 404 codes/pages or other HTTP non-200 codes/pages and Content Spoofing/Text Injection on these pages.
  • Fingerprint and other ways to detect versions that are disclosed on common/public services.
  • Clickjacking and issues that are only exploitable through clickjacking.
  • Lack of Secure/HTTP-Only flags on non-sensitive Cookies.
  • OPTIONS HTTP method enabled.
  • anything related to HTTP security headers, e.g.:
    • Strict-Transport-Security.
    • X-Frame-Options.
    • X-XSS-Protection.
    • X-Content-Type-Options.
    • Content-Security-Policy.
  • SSL Configuration Issues:
    • SSL forward secrecy not enabled.
    • weak/insecure cipher suites.
  • SPF, DKIM, DMARC issues.
  • Host header injection.
  • Reporting older versions of any software without proof of concept or working exploit.
  • Information leakage in metadata.
  • Systems and protocols that can be used in DDoS attacks.