ProjectBalm

Description

This bounty is part of the Atlassian Marketplace Bounty Program ProjectBalm produces Risk Register, an app that allows customers to record risks, assess their magnitude, assign them to team members, comment on them, and collaborate with others on their treatment. Quick Links Risk Register App Focus Areas Below is a list of some of the vulnerability classes that we are seeking reports for: • Server Security Misconfiguration • Server-Side Injection • Broken Authentication and Session Management • Sensitive Data Exposure • Insecure OS/Firmware • Broken Cryptography • Automotive Security Misconfiguration • Cross-Site Scripting (XSS) • Broken Access Control (BAC) • Cross-Site Request Forgery (CSRF) • Application-Level Denial-of-Service (DoS) • Client-Side Injection • Unvalidated Redirects and Forwards • Insufficient Security Configurability • Insecure Data Storage • Insecure Data Transport • Privacy Concerns • External Behavior • Lack of Binary Hardening • Network Security Misconfiguration • Mobile Security Misconfiguration • Indicators of Compromise

Targets

Rules, Exclusions, and Scopes Any domain/property of ProjectBalm 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 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: Create a Jira Cloud Instance 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" Click on Jira Settings Click on Apps Type “Risk Register” in search box Click on “Try it free” Following installation instructions on screen. Further documentation is available here 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. • Using Components with Known Vulnerabilities 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. 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 ProjectBalm 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 ProjectBalm 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. ProjectBalm 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 ProjectBalm’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