Kaleido

Description

No technology is perfect and Kaleido believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. We are excited for you to participate as a security researcher to help us identify vulnerabilities in our assets. Good luck, and happy hunting! 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 Kaleido not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in scope, but it demonstrably belongs to Kaleido, you can report it here. However, be aware that it is ineligible for rewards or points-based compensation. 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 Kaleido team is currently only paying rewards for P1 and P2 vulnerabilities. The Kaleido 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 We will not accept rate limiting bypass submissions, except where you are able to bypass OTP controls. 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 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.