If you believe you have found a security issue that meets our definition of a vulnerability, please submit the report to our security team via one of the methods below:
If you are a customer:
- Contact our support team
If you are a security researcher:
- Email email@example.com
Please include the following information in your report:
- Type of issue (cross-site scripting, SQL injection, remote code execution, etc.)
- The potential impact of the vulnerability (i.e. what data can be accessed or modified)
- Step-by-step instructions to reproduce the issue
- Any proof-of-concept or exploit code required to reproduce
If you wish to encrypt your submission with our PGP key, please download it here.
We are unable to respond to bulk reports generated by automated scanners. If you identify issues using an automated scanner, it is recommended that you have a security practitioner review the issues and ensure that the findings are valid before submitting a vulnerability report to Loop11.
Definition of a Vulnerablity
Loop11 considers a security vulnerability to be a weakness in our product or infrastructure that could allow an attacker to impact the confidentiality, integrity, or availability of the product or infrastructure.
We do not consider the following types of findings to be security vulnerabilities:
- Presence or absence of HTTP headers (X-Frame-Options, CSP, nosniff, etc.). These are considered security best practices and therefore we do not classify them as vulnerabilities.
- Missing security-related attributes on non-sensitive cookies. Loop11 product may set certain security-related attributes on cookies used on our applications. The absence of these headers on non-sensitive cookies is not considered a security vulnerability.
- Exposed stack traces. We do not consider stack traces by themselves to be a security issue. If you find that a stack trace details personally identifiable information or user generated content, please submit a report detailing the issue.
Loop11 makes it a priority to resolve any security vulnerabilities in our product and infrastructure within the resolution timeframes below.
- Critical severity bugs (CVSS v2 score >= 8, CVSS v3 score >= 9) to be fixed within 2 weeks of being reported
- High severity bugs (CVSS v2 score >= 6, CVSS v3 score >= 7) to be fixed within 4 weeks of being reported
- Medium severity bugs (CVSS v2 score >= 3, CVSS v3 score >= 4) to be fixed within 6 weeks of being reported
- Low severity bugs (CVSS v2 score < 3, CVSS v3 score < 4) to be fixed within 25 weeks of being reported
Loop11 follows coordinated vulnerability disclosure and requests, to protect our customers, that anyone reporting a vulnerability to us does the same.