Pexels

Description

Guidelines We require that all researchers: Make a every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing Perform research only within the scope set out below Use the identified communication channels to report vulnerability information to us Use your @bugcrowdninja email when testing Thank you for participating, it is your work that will help to keep us secure. Ratings/Rewards: For the initial prioritization/rating of findings, this program will use the Bugcrowd Vulnerability Rating Taxonomy . However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.

Targets

Testing is only authorized on the targets listed as In-Scope. Any domain/property of Canva not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you believe you've identified a vulnerability on a system outside the scope, please reach out to [email protected] before submitting. Credentials Please sign up for an account using your @bugcrowdninja.com email address. For more info regarding @bugcrowdninja email addresses, see here . Focus Areas The Canva team is currently only paying rewards for vulnerabilities P3 and higher. The Canva team is particularly concerned with the impact that can be demonstrated from a given vulnerability - for example they are less interested in seeing XSS generated alert boxes and more interested in understanding how the attack can be used to steal cookies/session/etc. Demonstrating the vulnerabilities impact will help ensure the severity of the issue is clear and demonstrating the full impact of the bug will influence its payout. Out of scope The use of noisy automated tools are out of scope for this engagement. Please keep requests limited to one request per second. We will not accept rate limiting bypass submissions, except where you are able to bypass OTP controls. 3rd party providers This is within reason. If you discover issues with our AWS or Cloudflare setup, we're going to want to know! But meh for generic vulnerability reports for third party providers such as: https://pagely.com/ https://zendesk.com/ http://mandrillapp.com Third-party add-ons Unsafe testing In the interest of the safety of our users, staff, the Internet at large, you must ensure that our users are in no way impacted by your testing. Please ensure you're testing using your own accounts, and do not access user data that you do not own in any way. The following are excluded from scope, and not eligible for a reward: If you discover user or employee credentials, cookies, or API keys (e.g. through dorking or otherwise), please do not attempt to verify them. We will validate credentials and evaluate impact Physical security tests Rubber hose cryptanalysis DoS / DDoS Phishing Malicious software/extensions Disclosure of non-sensitive information, such as product/framework version ID enumeration (such as user, design, folder, etc) without any further impact Disclosure of users information that is publicly available Insecure cookie settings for non-sensitive cookies Findings from applications or systems not listed in the ‘Targets’ section Functional, UI and UX bugs and spelling mistakes Reports based on product/protocol version without a proof of concept of exploiting the vulnerability Issues only affecting browsers that Canva does not support, docs located here Methods to bypass review of uploaded content. The review is not a security control, but an anti-abuse measure. We are specifically not paying for issues that have been identified by internal testing. Safe Harbor: When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via [email protected] before going any further.