VULNERABILITY DISCLOSURE POLICY
If a user has identified a potential security flaw in our infrastructure or software, pleaseÂ let us knowÂ within 24 hours using GPG encryption. LEIBOX will triage the issue and get back to the user within five business days.
Before reporting, please review the following information, including our responsible disclosure policy, scope, reward information, and other guidelines.
Responsible Disclosure Policy
LEIBOX is proud to base our responsible disclosure policy on theÂ https://disclose.io/vulnerability disclosure framework. Security is one of our core tenets at LEIBOX, and LEIBOX value the input of security professionals acting in good faith to help us maintain a high standard for the security and privacy of our users, including encouraging responsible vulnerability research and disclosure. This Policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what the user can expect from us in return.
When working with us, according to this Policy, the user can expect us to:
- Extend Safe Harbor for the user vulnerability research that is related to this Policy.
- Work with the user to understand and validate the user report, including timely initial response to the submission.
- Work to remediate discovered vulnerabilities promptly.
- Recognize the user contribution to improving our security if the user is the first to report a unique vulnerability, and the user report triggers a code or configuration change. This recognition may result in an award of financial compensation at LEIBOXâ€™s discretion if allowable under regulatory, compliance, and legal requirements.
To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attack, LEIBOX asks that the user:
- Play by the rules, including following this Policy, as well as any other relevant agreements.
- Politely report any vulnerability the user has discovered promptly to the LEIBOX information security team. LEIBOX reserve the right to disqualify individuals from the program for malicious, disrespectful or disruptive behaviour.
- Include detailed information, including the process of replication, for the security issue in question.
- Do not engage in the repeated submission of rejected, low-quality, or automated vulnerability reports.
- Do not access, modify, destroy, save, transmit, alter, transfer, use or view data belonging to anyone other than the user. If a vulnerability provides unintended access to data, please cease testing, purge local information, and submit a report immediately.
- Avoid violating the privacy of others, disrupting our systems, destroying data or harming the user experience.
- Keep the details of any discovered vulnerabilities confidential, according to the Disclosure Policy. Uncoordinated public disclosure of vulnerability may result in disqualification from this program.
- Use only the official channels designated (see â€śReportingâ€ť) to discuss vulnerability information with us.
- Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope.
- Do not engage in extortion, threats, or other tactics designed to elicit a response under duress. LEIBOX will not allow safe harbour or award rewards for vulnerability disclosure conducted under threat of full disclosure, exposure of data, or withholding of vulnerability information.
When conducting genuine in scope vulnerability research according to this Policy, LEIBOX considers this research to be:
- Authorized following the Computer Fraud and Abuse Act (CFAA) (or similar state laws), and LEIBOX will not initiate or support legal action against you for accidental, ethical faith violations of this Policy when conducting genuine vulnerability research.
- Exempt from the Digital Millennium Copyright Act (DMCA), and LEIBOX will not bring a claim against you for circumvention of technology controls when conducting genuine vulnerability research according to this Policy.
- Exempt from restrictions in our Terms & Conditions that would interfere with conducting genuine vulnerability security research, and LEIBOX waives those restrictions on a limited basis for genuine vulnerability research done under this Policy.
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
The user is expected, as always, to comply with all applicable laws.
If at any time the user has concerns or are uncertain whether the user security research is consistent with this Policy, please submit a report through one of our official Reporting channels before going any further.
At this time, the following services and applications are in-scope:
- The leibox.org website and infrastructure.
- The LEIBOX Foundry bug bounty infrastructure.
- Any public (Internet-facing) infrastructure owned and operated by LEIBOX.
- Examples include firewalls, networking devices, compute instances and proxies.
- Any public Email systems or infrastructure operated and managed by LEIBOX.
- Public cloud storage accounts. (e.g. AWS S3 buckets, Azure data blobs)
- Public cloud computes servers. (e.g. AWS EC2 instances, Azure Virtual Machines)
- Anything with significant impact across our entire security posture or infrastructure.
Out Of Scope
- Attacks designed or likely to degrade, deny, or adversely impact services or user experience (e.g., Denial of Service, Distributed Denial of Service, Brute Force, Password Spraying, Spam).
- Attacks designed or likely to destroy, corrupt, make unreadable (or attempts therein) data or information that does not belong to you.
- Attacks designed or likely to validate stolen credentials, credential reuse, account takeover (ATO), hijacking, or other credential-based techniques.
- The user is intentionally accessing data or information that does not belong to the user beyond the minimum viable access necessary to demonstrate the vulnerability.
- Performing physical, social engineering, or electronic attacks against LEIBOX personnel, offices, wireless networks, or property.
- Security issues in third-party applications, services, or dependencies that integrate with LEIBOX products or infrastructure that do not have demonstrable proof of concept for the vulnerability (e.g., libraries, SAAS services).
- Security issues or vulnerabilities created or introduced by the reporter (e.g., modifying a library LEIBOX rely on to include a vulnerability for the sole purpose of receiving a reward).
- Attacks performed on any systems not explicitly mentioned as authorized and in-scope.
- Reports generated from automated vulnerability assessment tools.
- Reports of missing â€śbest practicesâ€ť or other guidelines which do not indicate a security issue.
- Attacks related to email servers, email protocols, email security (e.g., SPF, DMARC, DKIM), or email spam.
- Missing cookie flags on non-sensitive cookies.
- Reports of insecure SSL/TLS ciphers (unless accompanied by working proof of concept).
- Reports of how the user can learn whether a given client can authenticate to a LEIBOX product or service.
- Reports of mappings between code names and client names.
- Reports of simple IP or port scanning.
- Missing HTTP headers (e.g. lack of HSTS).
- Email security best practices or controls (e.g. SPF, DKIM, DMARC).
- Software or infrastructure bannering, fingerprinting, or reconnaissance with no proven vulnerability.
- Clickjacking or self-XSS reports.
- Reports of publicly resolvable or accessible DNS records for internal hosts or infrastructure.
- Reports of user-provided remote code execution in sandboxed environments (e.g., Product Features).
- Domain-based phishing, typosquatting, punycodes, bitflips, or other techniques.
- Violating any laws or breaching any agreements (or any reports of the same).
LEIBOX provides rewards to vulnerability reporters at its discretion. Our minimum reward is USD 250. There is no maximum reward. Reward amounts may vary depending upon the severity of the vulnerability reported and quality of the report.
LEIBOX will only reward the first reporter of vulnerability and only if a discovered vulnerability is deemed to be in scope and discovered and reported in compliance with this Policy.
To report a potential security issue or vulnerability, please follow this reporting process:
- Compile as much technical information as possible, including steps to reproduce and validate the issue.
- Encrypt the email contents using a GPG key.
- Notify the LEIBOX Computer Incident Response Team (CIRT) within 24 hours of discovery by emailingÂ firstname.lastname@example.org. Please provide the best means of return communication.
- Allow up to 5 business days for confirmation of the reported issue.