Octopus

Description

Octopus Deploy invites you to test and help secure our primary publicly facing assets - focusing first on our primary web application. We appreciate your efforts and hard work in making the internet (and Octopus Deploy) more secure, and look forward to working with the researcher community to create a meaningful and successful bug bounty program. Good luck and happy hunting! What you should know before you start Ensure that you use your @bugcrowdninja.com email address when you’re testing our assets, any use of other email addresses may be treated as malicious and blocked. Ensure that you understand the targets, scopes, exclusions, and rules below. Please feel free to reach out and ask questions to clarify. We want you to feel as confident as possible. 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. Please see below for any deviations from the standard VRT. Employees, Contractors, Interns, and immediate family members are not eligible to receive rewards from our public-facing bug bounty programs. This restriction exists because employees may have access to internal systems, non-public information, or responsibilities that could create an actual, potential, or perceived conflict of interest. Employees who identify potential vulnerabilities must report them internally to the Security Operations team via [email protected].

Targets

Testing is only authorised on the targets listed as in-scope. Any domain/property of Octopus not listed in the targets section is out of scope. This includes any/all subdomains not listed above. Target Info Credentials: Please sign up for an account using your @bugcrowdninja.com email address. For more info regarding @bugcrowdninja email addresses, see here . When getting started, click the sign-in URL at https://octopus.com/register?registerReturnUrl=%2Fsignin and register there. Focus Areas Ultimately, we want to allow our customers to have a safe environment in which to manage their accounts, access our documentation, and manage their instances. Therefore, we're interested in traditional web application vulnerabilities, as well as other vulnerabilities that can have a direct impact on our customers. Below is a list of some of the vulnerability classes that we are seeking reports for: 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 Out of Scope and Other Exclusions To be as clear as possible, the following are also out of scope for testing : Subdomain takeover. WAF Bypasses (Octopus is currently reworking their WAF and not accepting any bypasses at this time). Secrets such as API keys or passwords obtained from external aggregation/indexed data sources (e.g. dehashed.com and intelx.io). Our self-hosted Octopus Deploy product, including its authentication and authorisation plugins. Our cloud-hosted Octopus Deploy product. Any of our closed or open-source tooling, build chain, public-facing repositories, email and IM servers, social media accounts, or third-party SaaS products that we use to deliver our services. Blind XSS must not return any user data you do not have access to (e.g., screenshots and cookies you don't own). When testing, please use the least invasive test possible (e.g. calling a 1x1 image or a nonexistent page on your web server). When testing, please exercise caution if injecting on any form that may be publicly visible, such as forums. Before injection, please ensure your payload can be removed from the site. If it cannot be easily removed, please check with support@bugcrowd before performing the testing. Pivoting and post-exploitation attacks are fine, particularly between test.octopus.com and test-account.octopus.com, so long as you aren’t attempting to destroy any infrastructure or data. Any internal or development services. The use of automated scanners is prohibited. Descriptive error messages (e.g. Stack Traces, application, and 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. Content spoofing. The presence of an application or web browser with "autocomplete" or "save password" functionality. Lack of Secure/HTTPOnly flags on non-sensitive Cookies. Lack of Security Speed Bump when leaving the site. Log in or Forgot Password page brute force and account lockout not enforced. Missing HTTP security headers, specifically (https://www.owasp.org/index.php/List_of_useful_HTTP_headers). For example: 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. SSL/TLS Issues. For example: 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 test websites. Self-XSS reports will not be accepted. Any XSS requiring local access (e.g., User-Agent Header injection) will not be accepted. The only exception is if you can show a working off-path MiTM attack that will allow the XSS to trigger. Vulnerabilities limited to old browsers will not be accepted (e.g. "this exploit only works in IE6/IE7"). Known vulnerabilities in used libraries (e.g. jQuery) unless you can prove exploitability. Missing or incorrect SPF records of any kind. Missing or incorrect DMARC records of any kind. Any source code disclosure. Information disclosure of non-confidential information (e.g. issue ID, project ID). Email bombing. Request flooding (e.g. pixel flooding(we consider this a DoS attempt)). Testing rate limits. Session cookies for https://account.octopus.com will be valid for up to 10 minutes after logging out. Please do not report on any session fixation/management vulnerabilities unless you can show an account takeover after 10 minutes. i.octopus.com contains a large number of files that are intended to be public. This includes but is not limited to files that are referenced Here (such as tax residency, W8-BEN-E form, bank attestation documents etc) on our trust resources page. If a document is identified that you believe does not fall into this category and should be bought to our attention - please make a submission and it will be reviewed. NPM name squatting is not considered a valid finding unless the package name is referenced as a dependancy by at least one octopus NPM package Testing is only authorised on the targets listed as in-scope. Any domain/property of Octopus not listed in the targets section is out of scope, including any/all subdomains not listed above. If you identify a security vulnerability on a not-in-scope target that demonstrably belongs to the Octopus organisation, you can report it to this program. However, while it is appreciated, it will ultimately be marked as "not applicable" and not eligible for monetary or points-based compensation. Other Rules You must ensure that your testing does not affect customer data in any way. Please ensure that you're being non-destructive while testing. In addition to the above, customer instances are not to be accessed in any way (i.e., no customer data is to be 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 (e.g., through a vulnerability), report it, but do not attempt to validate whether/that it works successfully. Use of any automated vulnerability scanners is prohibited. Reports must 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 and DOCX) will be asked to be resubmitted in plain text. Grants/awards are at Octopus Deploy's discretion, and we withhold the right to grant, modify, or deny grants. Please do not use social engineering, phishing, or unauthorised access to infrastructure. Please do not test the physical security of Octopus Deploy offices, employees, equipment, etc. This bounty follows Bugcrowd’s standard disclosure terms. Public Disclosure Before publicly disclosing an issue, we require that you first request permission from us. Octopus Deploy 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. Safe Harbor: When conducting vulnerability research according to this policy, we consider this research to be: Authorised in accordance with the Computer Fraud and Abuse Act (CFAA) (and 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. Lawful and helpful to the overall security of the Internet and conducted in good faith. Expected to comply with all applicable laws. If you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via [email protected] before going further.

In Scope (in scope)

Please note that dependencies with known issues within the GitHub are not considered valid without a working proof of concept that affects the actual platform. In addition, API keys on their own are not considered valid. In order to have a valid leaked API key, the domain URL must be referencing an Octopus domain that fits *.octopus.app. Any API keys with localhost or test within their name are considered invalid.

Out of scope targets (out of scope)

Targets in this list are OUT OF SCOPE. Please also review the brief information below for more details, it contains important information and also lists further areas that are considered out of scope for this bounty.