At Leaseweb, 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. No technology is perfect, and Leaseweb believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you have identified a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly.
Guidelines for responsible disclosure
- Let us know as soon as possible upon discovery of a potential security issue, and we will make every effort to quickly resolve the issue.
- Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
- Only use official communication channels: Do not use personal emails, social media accounts, or other private connections to contact a member of a security team in regards to vulnerabilities or any program related issues, unless you have been instructed to do so by the program.
- No unauthorized impersonation: any unauthorized attempts to socially engineer another party through impersonation of a Leaseweb employee, another hacker, or a security team will not be tolerated.
- If you comply with all conditions set in the guidelines, we will not take any legal action against you regarding this report.
- Your report will be confidential, we will not share your personal information with third parties without prior consent, unless this is necessary to comply with a legal obligation.
To show our appreciation of responsible security researchers, Leaseweb offers bounties for reports of qualifying security vulnerabilities. Bounties will be awarded in the form of financial compensations. The amount that is rewarded per bounty is at discretion of Leaseweb and will be communicated after validation of the security vulnerability.
To qualify for a reward, you must:
- Be the first reporter of the vulnerability.
- Follow the guidelines as described on this page.
- Not publicly disclose the vulnerability prior to our resolution.
- Provide a working proof of concept that exploits the security issue
- Solely use your created accounts and not access data of other users
While researching, we would like to ask you to refrain from:
- Social engineering (including phishing) of Leaseweb staff or contractors
- Any physical attempts against Leaseweb property or data centers
- Physical attack on the infrastructure
- Denial of service
- Login/Logout CSRF
- Self-XSS (we require evidence on how the XSS can be used to attack another Leaseweb user)
- Miss of rate limits
- Report from automated tools and scans
- Bugs in 3rd party software
- X-Frame-Options related
- Missing cookie flags on non-sensitive cookies
- Missing security headers which do not lead directly to a vulnerability (unless you deliver a PoC)
- DKIM/SPF/DMARC issues (we are aware they are missing and working on resolution)
- Version exposure (unless you deliver a PoC of working exploit)
- Directory listing with already public readable content