Flourish

Description

Flourish is an easy to use data visualization and story-telling platform. Here at Flourish we believe no technology is perfect, and we want to have the crowd find security vulnerabilities for us to fix! We take the security of our systems seriously, and we value the security researcher community. Your responsible disclosure of security vulnerabilities by security researchers helps us ensure the security and privacy of our users. Guidelines We require that all researchers: -Include a bug URL in the submission details otherwise the submission will not be accepted 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 address when testing Use an X-BugBounty: username header to uniquely tag all attack traffic 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 Flourish 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 . Access All targets are publicly accessible. Focus Areas The main flourish.studio web application, and *.xyzbmojn.net assets Known issues CSRF vulnerabilities in components will be treated as P4 unless you are able to demonstrate ATO. We have reports of XSS on templates.flourish.studio, preview.flourish.studio, demos.flourish.studio and flo.uri.sh. The fix for this will likely be the same. If a unique report has the same root cause fix it will be a duplicate of the original issue. Reports will be only considered if they are able to prove escalated impact. Any report that describes a complicated way to achieve something that could alternatively be achieved just by uploading a custom template to Flourish will be rejected. Out of Scope We will not accept rate limiting bypass submissions, except where you are able to bypass OTP controls. Untrusted User Content Domains As part of the Flourish product, the below domains are used to host visualisations from third parties, and as such any vulnerability reports for these domains must show proof of impact for their vulnerabilities, as basic vulnerability PoCs (such as simple XSS or Open Redirect) will not be accepted or rewarded. flo.uri.sh flourish-user-templates.com flourish-user-preview.com 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 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.