At JT, 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 customers and our systems.
Please do the following:
- E-mail your findings to firstname.lastname@example.org.
- 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;
- 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; and
- Only email the responsible disclosure mailbox with information or requests related to your findings, any communication outside of this mailbox will not be monitored or actioned.
What we promise
- If you have followed the instructions above, we will not take any legal action against you in regard to the report;
- We will not share your personal details with third parties without your authorisation, unless required in order to do so to comply with legal obligations; and
- We will make reasonable efforts to respond quickly, to confirm receipt of the vulnerability report and to provide a summary of our initial findings.
JT cannot currently offer a bug bounty for vulnerabilities disclosed. We will, however, make efforts to thank every researcher that submits a vulnerability that helps us to improve our security.
Out of Scope
Some findings do not need to be disclosed as they have low security impact. This section contains a listing of issues found to be commonly reproducible and reported. Vulnerabilities included within the following categories do not need to be notified:
- 404 HTTP page errors
- Banner disclosures
- SSL/TLS insecure ciphers
- Missing HTTP security headers
- TRACE/OPTIONS HTTP methods enabled
- Logout CSRF
- Clickjacking attacks
- Public files or directories disclosure (readme.html, robots.txt, sitemap.xml)
- Secure and HTTPOnly cookie flags
We strive to remediate all identified vulnerabilities as quickly as possible, and where applicable, we would like to play an active role in the ultimate publication on the vulnerability after it has been remediated.