Opsgenie

Description

Opsgenie is a modern incident management platform for operating always-on services, empowering Dev & Ops teams to plan for service disruptions and stay in control during incidents. With over 200 deep integrations and a highly flexible rules engine, Opsgenie centralizes alerts, notifies the right people reliably, and enables them to collaborate and take rapid action. Throughout the entire incident lifecycle, Opsgenie tracks all activity and provides actionable insights to improve productivity and drive continuous operational efficiencies. Get Started (tl;dr version) Testing for Opsgenie is to be performed on https://*.opsgenie.com using free-trial accounts. Do not access, impact, destroy or otherwise negatively impact Opsgenie customers, or customer data in anyway. Ensure that you use your @bugcrowdninja.com email address. Ensure you understand the targets, scopes, exclusions, and rules below. Quick Links Opsgenie Links Website https://docs.opsgenie.com/docs/welcome https://docs.opsgenie.com/docs/opsgenie-quick-start-guide https://docs.opsgenie.com/docs/new-user-guide Docs https://docs.opsgenie.com/ For real time support you can also use Intercom chat bubble on bottom right of www.opsgenie.com API Docs https://docs.opsgenie.com/docs/api-overview https://docs.opsgenie.com/docs/api-access-management https://docs.opsgenie.com/docs/authentication https://docs.opsgenie.com/docs/alert-api https://docs.opsgenie.com/docs/user-api Mobile apps (Android) https://play.google.com/store/apps/details?id=com.ifountain.opsgenie (iOS) https://itunes.apple.com/us/app/opsgenie/id528590328 Focus Areas Authentication Session Management HTTP and Cookie Security Multi Tenant Data Leakage/Access Server-side Remote Code Execution (RCE) Server-Side Request Forgery (SSRF) Stored/Reflected Cross-site Scripting (XSS) Injection XML External Entity Attacks (XXE) Access Control & Authorization Vulnerabilities Path/Directory Traversal Issues File Upload & File hosting Ensure you review the out of scope and exclusions list for further details. ** Cross Instance Data Leakage/Access refers to unauthorised data access between instances. Creating Your Instance Researchers can sign up here: https://www.atlassian.com/software/opsgenie/try Note: Remember to use your @bugcrowdninja.com email address !! Do not forget to verify your account by clicking on the link via email, some features will not work until verification is complete. !! Additional documents: https://docs.opsgenie.com/docs/welcome https://docs.opsgenie.com/docs/opsgenie-quick-start-guide https://docs.opsgenie.com/docs/quick-set-up-video https://docs.opsgenie.com/docs/new-user-guide https://docs.opsgenie.com/docs/users Disclosure Request Guidance Submissions that meet the following requirements will be considered for disclosure upon request: The submission has been accepted The reported vulnerability has been fixed and released in production The submission does not regard a customer instance or a customer’s account

Targets

Rules, Exclusions, and Scopes Any domain/property of Opsgenie not listed in the targets section is strictly out of scope (for more detailed information please see the out of scope and exclusions sections below). Researchers should use their @bugcrowdninja.com email address when signing up for an account. All resources within your instance are in scope (see below for exclusions), this includes the REST API. 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. Screen shots, 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. Customer cloud instances and data are explicitly out of scope. Any repository that you are not an owner of - do not impact Opsgenie customers in any way. Any Opsgenie billing system. However, specific endpoints that are used inside of a target are in scope. For example, if a REST endpoint is proven to be called from one of the targets, then that endpoint is considered to be in scope. However, all other endpoints are not considered to be in scope, as they are not called from the instance at any stage. Any internal or development services Third party add-ons/integrations others than those listed in the targets from the marketplace are strictly excluded (vulnerabilities that exist within third-party apps in any way) - we will pass on any vulnerabilities found, however, they will not be eligible for a bounty. The following finding types are specifically excluded from the bounty 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. Disclosure of known public files or directories, (e.g. robots.txt). Clickjacking and issues only exploitable through clickjacking. 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, Renegotiation attack. 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 outdated browsers will not be accepted (i.e. "this exploit only works in IE6/IE7"). Ensure you're testing on the latest versions of your browser. Known vulnerabilities in used libraries, or the reports that Opsgenie 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. This includes DMARC. 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 Lack of rate limiting CSV Injection 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. Sufficiently similar access control issues should be grouped in one report. Atlassian defines “sufficiently similar” as issues that use the same configuration for bypassing a particular control, which may be used on multiple related vulnerable endpoints or actions (User X can Create/Delete/Edit Resource Y). Grants/awards are at the discretion of Atlassian 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 Opsgenie offices, employees, equipment, etc. This bounty follows Bugcrowd’s standard disclosure terms. Reporting Guidelines Where applicable, please include the following information. This will greatly assist in the triage, validation, and acceptance processes and will result in more clear security risk communication and timely report acceptances. Brief summary (please include product versions affected/tested) Prerequisites (including any products, user privileges, tools required, files prepared, web server configurations, or any other initial conditions to prior to initiating the proof of concept) Reproduction steps including vulnerable endpoints, parameters, payloads used, source of any scripts used, or command line inputs (burp requests, screenshots and recordings are highly encouraged) Expected results/behavior vs actual results/behavior (include any formal documentation, resources, or links that state the expected behavior) Assessed security impact (as it relates to the Confidentiality, Integrity, and/or Availability of the product) Possible mitigations, fixes, or security controls Public Disclosure At Atlassian, one of our values is Open Company, No Bullshit, we believe that vulnerability disclosure is a part of that value. We hold ourselves to the security bug fix service level objectives, found here , and will accept disclosure requests in the bug bounty program after the issue has been fixed and released in production. However, if the report contains any information regarding a customer instance or data the request will be rejected. If you are planning to disclose outside of the bug bounty, we ask that you give us reasonable notice and wait until the associated SLO has passed. 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. Rewards: Any finding that is not listed in the above tiers can still be reported via this program. These reports will be rewarded as kudos only reports - any payout is at the discretion of the Opsgenie Security Team. Note: Opsgenie uses CVSS to consistently score security vulnerabilities. Where discrepancies between the VRT and CVSS score exist, Opsgenie will defer to the CVSS score to determine the priority.