Last updated
Dec 13, 2024
Introduction
This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to V7 (the "Organisation"). We recommend reading this policy fully before reporting a vulnerability and always acting in compliance with it.
We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer any guarantees of monetary reward for vulnerability disclosures.
Reporting
If you believe you have found a security vulnerability, please submit your report to us using the following email: security@v7labs.com. See more information at https://v7labs.com/.well-known/security.txt.
In your report please include details of:
The website, IP, or page where the vulnerability can be observed.
A brief description of the type of vulnerability (e.g., “XSS vulnerability”).
Steps to reproduce, including a benign, non-destructive proof of concept.
This ensures the report can be triaged quickly and accurately, reducing the likelihood of duplicate reports or malicious exploitation, such as sub-domain takeovers.
What to expect
After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days. We’ll also aim to keep you informed of our progress.
Priority for remediation is assessed by looking at the impact, severity and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to inquire on the status but should avoid doing so more than once every 14 days. This allows our teams to focus on the remediation.
We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately. Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify guidance to affected users, so please do continue to coordinate public release with us.
Guidance
You MUST NOT:
Break any applicable laws or regulations.
Access unnecessary, excessive, or significant amounts of data.
Modify data in the Organisation's systems or services.
Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
Attempt or report any form of denial-of-service attack (e.g., overwhelming a service with high request volumes).
Disrupt the Organisation’s services or systems.
Submit reports detailing non-exploitable vulnerabilities or “best practice” deviations (e.g., missing security headers).
Submit reports detailing TLS configuration weaknesses (e.g., "weak" cipher suite support or presence of TLS 1.0).
Communicate vulnerabilities or associated details through any channel other than those specified in the published security.txt.
Social engineer, "phish," or physically attack the Organisation’s staff or infrastructure.
Demand financial compensation in exchange for disclosing vulnerabilities.
You MUST:
Always comply with data protection rules and must not violate the privacy of the Organisation’s users, staff, contractors, services or systems. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).
Legalities
This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the Organisation or partner organisations to be in breach of any legal obligations.