Details

Responsible Disclosure Program

Veeam is the leader in backup, recovery and data management solutions that deliver Modern Data Protection. We provide a single platform for cloud, virtual, physical, SaaS and Kubernetes environments. Our customers are confident their apps and data are protected and always available with the most simple, flexible, reliable and powerful platform in the industry.

We value the critical role that the security community plays in helping us protect the confidentiality, integrity, and availability of Veeam's software, services, and information. If you have information about security vulnerabilities within the scope of this program, please use this form to submit a report.

Disclosure Policy

Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
Follow HackerOne's disclosure guidelines.

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
Do not test the physical security of Veeam property.
Do not include any information in vulnerability reports, including in any attachments, that may identify an individual (such as a name, contact information, IP address or other similar information).
The preferred language for submissions is English, if a submission is made in a different language the submission may be discarded and/or delayed.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

Directory Browsing Vulnerability on repository.veeam.com. The system is designed this way to provide files to customers.
Virtual Chat Assistants / Chatbots found on our web domains are specifically out of scope.
Customer support request forms (i.e. - Veeam Customer Portal Cases and Case Escalation Forms) are out of scope.
Clickjacking on pages with no sensitive actions
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
Attacks requiring MITM or physical access to a user's device.
Previously known vulnerable libraries without a working Proof of Concept.
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
Missing best practices in SSL/TLS configuration.
Any activity that could lead to the disruption of our service (DoS).
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Rate limiting or bruteforce issues on non-authentication endpoints
Missing best practices in Content Security Policy.
Missing HttpOnly or Secure flags on cookies
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
Tabnabbing
Issues that require unlikely user interaction

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Legal Notice

Please note that both HackerOne's disclosure guidelines and this Policy are subject to changes or termination at any time. Please check the current version of document before the submission of your report.
To protect our customers, Veeam reserves a right not to disclose or confirm publicly any security vulnerability until Veeam has conducted a full analysis of such vulnerability and issued any necessary fixes or mitigations.
By submitting your report, you grant Veeam, its subsidiaries, affiliates and contractors a perpetual, worldwide, exclusive, irrevocable, no charge license to sublicense, copy, distribute, display, perform, transmit, publish or otherwise use the report or any part thereof.
So that Veeam may utilize your report you also shall notify Veeam is any of the material in your report is your own work or is covered by the intellectual property rights of third parties. Not notifying Veeam means that you've represented that no third-party intellectual property rights are involved.
You understand that nothing in Policy shall be deemed to constitute the grant to you of any license or other right to or in respect of any Veeam or third-party product, service, patent, trademark, trade secret, or other intellectual property.
By submitting your report, you provide Veeam with your consent to process personal data contained in the report (if any) in accordance with Veeam Privacy Policy.

Thank you for helping keep Veeam and our users safe!

Responsible Disclosure Program

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.

Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.

When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).

Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.

Social engineering (e.g. phishing, vishing, smishing) is prohibited.

Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

Do not test the physical security of Veeam property.

Do not include any information in vulnerability reports, including in any attachments, that may identify an individual (such as a name, contact information, IP address or other similar information).

The preferred language for submissions is English, if a submission is made in a different language the submission may be discarded and/or delayed.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

Directory Browsing Vulnerability on repository.veeam.com. The system is designed this way to provide files to customers.

Virtual Chat Assistants / Chatbots found on our web domains are specifically out of scope.

Customer support request forms (i.e. - Veeam Customer Portal Cases and Case Escalation Forms) are out of scope.

Clickjacking on pages with no sensitive actions

Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

Attacks requiring MITM or physical access to a user's device.

Previously known vulnerable libraries without a working Proof of Concept.

Comma Separated Values (CSV) injection without demonstrating a vulnerability.

Missing best practices in SSL/TLS configuration.

Any activity that could lead to the disruption of our service (DoS).

Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

Rate limiting or bruteforce issues on non-authentication endpoints

Missing best practices in Content Security Policy.

Missing HttpOnly or Secure flags on cookies

Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).

Tabnabbing

Issues that require unlikely user interaction

Safe Harbor

Legal Notice

Please note that both HackerOne's disclosure guidelines and this Policy are subject to changes or termination at any time. Please check the current version of document before the submission of your report.

To protect our customers, Veeam reserves a right not to disclose or confirm publicly any security vulnerability until Veeam has conducted a full analysis of such vulnerability and issued any necessary fixes or mitigations.

By submitting your report, you grant Veeam, its subsidiaries, affiliates and contractors a perpetual, worldwide, exclusive, irrevocable, no charge license to sublicense, copy, distribute, display, perform, transmit, publish or otherwise use the report or any part thereof.

So that Veeam may utilize your report you also shall notify Veeam is any of the material in your report is your own work or is covered by the intellectual property rights of third parties. Not notifying Veeam means that you've represented that no third-party intellectual property rights are involved.

You understand that nothing in Policy shall be deemed to constitute the grant to you of any license or other right to or in respect of any Veeam or third-party product, service, patent, trademark, trade secret, or other intellectual property.

By submitting your report, you provide Veeam with your consent to process personal data contained in the report (if any) in accordance with Veeam Privacy Policy.

Thank you for helping keep Veeam and our users safe!