Stiltsoft

Description

This bounty is part of the Atlassian Marketplace Bounty Program Stiltsoft is a highly motivated team of developers with rich experience in the Atlassian Ecosystem since 2010. As an Atlassian Platinum Marketplace Partner, we build high-quality apps that extend the capabilities of Confluence, Jira, and Bitbucket, helping businesses streamline their workflows. With 15,000 companies across 80+ countries trusting our solutions, security remains a top priority in everything we do. Get Started (tl;dr version) Do not access, impact, destroy or otherwise negatively impact Stiltsoft or Atlassian customers, or customer data in any way. Ensure that you use your @bugcrowdninja.com email address. Please do not test marketplace.atlassian.com , but install our apps in your Jira/Confluence/Bitbucket instance and test the apps themselves. Do not post reviews for our apps on marketplace.atlassian.com . Failure to adhere to this will result in not receiving any reward for any of your submissions and possible removal from the program. Ensure you understand the targets, scopes, exclusions, and rules below. Quick Links Table Filter and Charts for Confluence (Cloud) Table Filter and Charts for Confluence (Data Center) Courses and Quizzes - LMS for Confluence (Cloud) Awesome Graphs for Bitbucket (Cloud) Awesome Graphs for Bitbucket (Data Center) TeamCity Integration for Jira (Cloud) Handy Macros for Confluence (Cloud) Handy Macros for Confluence (Data Center) Spreadsheet Issue Field Editor Smart Attachments for Jira (Cloud) Webhook Manager for Confluence (Cloud) LaTeX Math for Confluence (Cloud) Checklist for Jira Cloud | Smart ToDo Lists (Cloud) Live Tables from CSV & JSON for Confluence Focus Areas Below is a list of some of the vulnerability classes that we are seeking reports for: Cross Instance Data Leakage/Access** Server-side Remote Code Execution (RCE) Server-Side Request Forgery (SSRF) Stored/Reflected Cross-site Scripting (XSS) Cross-site Request Forgery (CSRF) SQL Injection (SQLi) XML External Entity Attacks (XXE) Access Control Vulnerabilities (Insecure Direct Object Reference issues, etc) Path/Directory Traversal Issues Ensure you review the out of scope and exclusions list for further details. ** Cross Instance Data Leakage/Access refers to unauthorized data access between instances. Please ensure you're being non-destructive whilst testing and are only testing using accounts and instances created via the instructions under "Creating your instance". Any testing/spamming live support portals or Marketplace sites will disqualify you and you will be banned from Atlassian programs. 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

Rules, Exclusions, and Scopes Any domain/property of StiltSoft not listed in the targets section is strictly out of scope (for more information please see the out of scope and exclusions sections below). Creating Your Instance Jira + Confluence Cloud Researchers should use the bugbounty-test-.atlassian.net namespace provided in the instructions below. Please do not create additional instances outside of this namespace for testing. To access the instance and start your testing (after you've read and understood the scope and exclusions listed below, of course) you can follow the below steps: Navigate to the checkout page here Click "Next" Complete the form, using the following format: bugbounty-test- Note that should be replaced with your own Bugcrowd username Click "Start now" Once your instance has been completed that's it - you can test away. Сonfluence Data Center Navigate to www.atlassian.com and download Confluence Data Center Install the product and generate a trial license for Confluence Install the Table Filter and Charts for Confluence app and generate a trial license for the app. Please use your [username]@bugcrowdninja.com email alias to get the license. Start testing Bitbucket Cloud Navigate to https://bitbucket.org/ and select "Log In" Select "Sign Up" and create an account with your @bugcrowdninja.com email address. Install the Awesome Graphs app Start testing Bitbucket Data Center Navigate to www.atlassian.com and download Bitbucket Data Center Install the product and generate a trial license for Bitbucket Install the Awesome Graphs for Bitbucket app and generate a trial license for the app. Please use your [username]@bugcrowdninja.com email alias to get the license. Start testing Out-of-Scope Anything not declared as a target or in scope above should be considered out of scope for the purposes of this bug bounty. However to help avoid grey areas, below are examples of what is considered out of scope. Authenticated access within a Bitbucket instance to contributor identity data through Awesome Graphs for Bitbucket Data Center is out of scope. Contributor records are instance-wide and are not filtered by repository permissions. This includes: emails of registered Bitbucket users already available on Bitbucket profile pages; contributor alias relationships returned by POST /rest/awesome-graphs/1.0/contributors/resolve ; names and email values returned by POST /rest/awesome-graphs/1.0/contributors/details , including identities without Bitbucket accounts and values indexed from private-repository commits the requester cannot access. Viewing the outdated data within the Table Filter and Charts app macros after changing the user permissions is out of scope in the cases below because the user has already viewed or exported the restricted data earlier: the space exported to PDF or Word the page tree exported to PDF or Word the Confluence Server mobile app the Confluence mobile site the Table Excerpt Include macro with the Output cached results option enabled. You can edit the storage of a Confluence page where the Handy Poll macro resides. This way, you can change names of variants and fake the voting results. Changes in the page storage will be reflected in the page history. Check the Handy Macros Cloud FAQ for more details. The case when a user can get emails of other Bitbucket users through the Awesome Graphs app is out of scope, because any Bitbucket user can get such emails on a user profile page in the Bitbucket Server and Data Center directly. Blind XSS must not return any user data that you do not have access to (e.g. screenshots, cookies that aren't owned by you, etc); when testing for blind XSS, please use the least invasive test possible (e.g. calling 1x1 image or nonexistent page on your webserver, etc). When testing, please exercise caution if injecting on any form that may be publicly visible - such as forums, etc. Before injection, please make sure your payload can be removed from the site. If it cannot be easily removed, please check with support@bugcrowd before performing the testing. No pivoting or post-exploitation attacks (i.e. using a vulnerability to find another vulnerability) are allowed on this program. DO NOT under any circumstance leverage a finding to identify further issues. Any StiltSoft website is out of scope for this bounty unless it is directly accessible from one of the targets or any associated services attached to the instance. Customer cloud instances and data are explicitly out of scope. Any repository that you are not an owner of - do not impact StiltSoft or Atlassian customers in any way. Any internal or development services. The following finding types are specifically excluded from the bounty Lack of Rate Limiting on any of the targets. The use of Automated scanners is strictly prohibited (we have these tools too - don't even think about using them) Descriptive error messages (e.g. Stack Traces, application or server errors). Fingerprinting / banner disclosure on common/public services. Clickjacking and issues only exploitable through clickjacking. Logout Cross-Site Request Forgery (logout CSRF). Content Spoofing. Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality. Lack of Secure/HTTPOnly flags on non-sensitive Cookies. Lack of Security Speedbump when leaving the site. Weak Captcha / Captcha Bypass. Login or Forgot Password page brute force and account lockout not enforced. Username / email enumeration. Missing HTTP security headers, specifically ( https://owasp.org/www-project-secure-headers/ ), e.g. Strict-Transport-Security. X-Frame-Options. X-XSS-Protection. X-Content-Type-Options. Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP. Content-Security-Policy-Report-Only. Cache-Control and Pragma HTTP/DNS cache poisoning. SSL/TLS Issues, e.g. SSL Attacks such as BEAST, BREACH, Renegotiation attack. SSL Forward secrecy not enabled. SSL weak/insecure cipher suites. Self-XSS reports will not be accepted. Similarly, any XSS where local access is required (i.e. User-Agent Header injection) will not be accepted. The only exception will be if you can show a working off-path MiTM attack that will allow for the XSS to trigger. Vulnerabilities that are limited to unsupported browsers will not be accepted (i.e. "this exploit only works in IE6/IE7"). A list of supported browsers can be found here . Known vulnerabilities in used libraries, or the reports that an Atlassian product uses an outdated third party library (e.g. jQuery, Apache HttpComponents etc) unless you can prove exploitability. Missing or incorrect SPF records of any kind. Missing or incorrect DMARC records of any kind. Source code disclosure vulnerabilities. Information disclosure of non-confidential information (e. g. issue id, project id, commit hashes). The ability to upload/download viruses or malicious files to the platform. Email bombing/Flooding/rate limiting. JWT in ajax requests ignores path and HTTP method. For some of our apps, we allow arbitrary HTML templates to be defined by administrators. Those could potentially be used for XSS attacks, however since only administrators have access we don't consider those as security threats. Rules You must ensure that customer data is not affected in any way as a result of your testing. Please ensure you're being non-destructive whilst testing and are only testing on instances that you own. In addition to above, customer instances are not to be accessed in any way (i.e. no customer data is accessed, customer credentials are not to be used or "verified") If you believe you have found sensitive customer data (e.g., login credentials, API keys etc) or a way to access customer data (i.e. through a vulnerability) report it, but do not attempt to successfully validate if/that it works. Only the latest version of a Server or Data Center app is eligible for a reward. All vulnerabilities/exploits must be proven to work in the latest version of the Atlassian Server or Data Center product. Any vulnerability found in a Cloud app is not eligible for a reward in the Server or Data Center app, and vice versa (i.e. no double dipping). The same is applicable for vulnerabilities found in a Server app that are not eligible for a reward in the Data Center app, and vice versa. Use of any automated tools/scanners is strictly prohibited and will lead to you being removed from the program (trust us, we have those tools too). Reports need to be submitted in plain text (associated pictures/videos are fine as long as they're in standard formats). Non-plain text reports (e.g. PDF, DOCX) will be asked to be resubmitted in plain text. Grants/awards are at the discretion of StiltSoft and we withhold the right to grant, modify or deny grants. But we'll be fair about it. Tax implications of any payouts are the sole responsibility of the reporter. Do NOT conduct non-technical attacks such as social engineering, phishing or unauthorized access to infrastructure. Do NOT test the physical security of StiltSoft offices, employees, equipment, etc. This bounty follows Bugcrowd’s standard disclosure terms. Public Disclosure Before disclosing an issue publicly we require that you first request permission from us. StiltSoft will process requests for public disclosure on a per report basis. Requests to publicly disclose an issue that has not yet been fixed for customers will be rejected. Any researcher found publicly disclosing reported vulnerabilities without StiltSoft's written consent will have any allocated bounty withdrawn and disqualified from the program. 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 submit a report through one of our Official Channels before going any further.