Report vulnerabilities

Report vulnerability

“At ChannelEngine, 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. ChannelEngine would like to ask you to help us better protect our clients and our product”.

Once discovering a vulnerability or a security incident we kindly ask you to do the following:
  • Send your findings to ChannelEngine via 'Report vulnerability' link at the top of this page. Encrypt your findings 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 any 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 component and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation and a simple proof of concept.

What we promise:
  • ChannelEngine security team 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, ChannelEngine will not take any legal action against you in regard to the report,
  • ChannelEngine will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,
  • In the public information concerning the problem reported, we commit to give your name the credit as the discoverer of the problem (unless you desire otherwise).
  • 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 and labelled as a vulnerability (Details TBD).
  • The amount of the reward will be determined based on the severity of the leak and the quality of the report.
  • ChannelEngine aims 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.


Out of scope:

ChannelEngine does not reward trivial vulnerabilities or bugs that cannot be abused. The following are examples of known and accepted vulnerabilities and risks that are outside the scope of the responsible disclosure policy:

  • HTTP 404 codes/pages or other HTTP non-200 codes/pages and Content Spoofing/Text Injection on these pages.
  • fingerprint version banner disclosure on common/public services.
  • disclosure of known public files or directories or non-sensitive information, (e.g. robots.txt).
  • clickjacking and issues only exploitable through clickjacking.
  • lack of Secure/HTTPOnly flags on non-sensitive Cookies.
  • OPTIONS HTTP method enabled.
  • anything related to HTTP security headers,
    • 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.