Opus Guard Marketplace Managed Bug Bounty Engagement

Description

This bounty is part of the Atlassian Marketplace Bug Bounty Program At Opus Guard we are simplifying information governance. We focus on compliance for retention management so you can keep what you need, and delete what you don’t. This means we scan every bit of content in your Atlassian Cloud products regularly and we automate the application of your retention policies, the deletion and purging of expired content, and produce a full audit trail for compliance and discovery purposes.

Targets

Testing is only authorized on the targets listed as in scope. Any domain/property of Opus Guard 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 demonstrably belongs to Opus Guard you can report it to this program. However, be aware that it is ineligible for rewards or points-based compensation. Focus Areas Below is a list of some of the vulnerability classes that we are seeking reports for: Cross Instance Data Leakage/Access (Unauthorized data access between instances) 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 ** Cross Instance Data Leakage/Access refers to unauthorized data access between instances. Rules, Exclusions, and Scopes Any domain/property of Opus Guard not listed in the targets section is strictly out of scope (for more information please see the out-of-scope and exclusions sections below). Credentials: 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. Creating Your Instance JIRA + Confluence Cloud 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 signup page and complete the sign up by email process here Click "Agree" 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. Proceed to the application's marketplace listing and install the respective application. There is a tab for installation instructions should you need guidance. 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. 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 web server, 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 Opus Guard website (e.g. opusguard.com) 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, or Atlassian customers in any way. Only the latest version of our products are eligible for a reward. Any internal or development services 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). HTTP 404 codes/pages or other HTTP non-200 codes/pages. Fingerprinting/banner disclosure on common/public services. Disclosure of known public files or directories, (e.g. robots.txt). Clickjacking and issues only exploitable through clickjacking. CSRF on forms that are available to anonymous users (e.g. the contact form). CSRF attacks that require knowledge of the CSRF token (e.g. attacks involving a local machine). 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. OPTIONS HTTP method enabled. Username/email enumeration. Missing HTTP security headers, specifically (https://www.owasp.org/index.php/List_of_useful_HTTP_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, and Renegotiation attacks. SSL Forward secrecy not enabled. SSL weak/insecure cipher suites. No Load testing (DoS/DDoS etc) is allowed on the instance. This includes application DoS as well as network DoS. 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 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 the above, customer instances are not to be accessed in any way (i.e. no customer data is accessed, and 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 Opus Guard 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 Opus Guard 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. Opus Guard 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 Opus Guard 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 create a ticket with Bugcrowd Support for clarification before proceeding.