Last updated
Work seamlessly with Octopus Deploy from the command line.
$ winget install --id OctopusDeploy.Cli --exact --version 2.20.1Run in Command Prompt, PowerShell, or Windows Terminal. Prompts for any agreements.
Octopus CLI uses MSI (WiX). The silent install switches are /quiet /norestart.
msiexec.exe /i octopus_2.20.1_windows_amd64.msi /quiet /norestart
For Intune admins
Automated application patching for Microsoft Intune. Pckgr keeps a curated library of 1,000+ apps continuously up-to-date in your tenant via Microsoft Graph - no manual repackaging, no chasing vendor sites.
Start free 30-day trialNo credit card required.
| Architecture | Type | Scope | Install | Download |
|---|---|---|---|---|
| x64 | MSI WiX | machine | Direct |
Copy a command tailored to that specific architecture, type, and scope - useful when winget would otherwise pick a different default.
11 known CVEs via NVD
In affected versions of Octopus Deploy it is possible to unmask variable secrets using the variable preview function
In Octopus Server after version 2022.1.1495 and before 2022.1.2647 if private spaces were enabled via the experimental feature flag all new users would have access to the Script Console within their private space.
In affected Octopus Server versions when the server HTTP and HTTPS bindings are configured to localhost, Octopus Server will allow open redirects.
When Octopus Server is installed using a custom folder location, folder ACLs are not set correctly and could lead to an unprivileged user using DLL side-loading to gain privileged access.
In Octopus Deploy through 2020.4.2, an attacker could redirect users to an external site via a modified HTTP Host header.
An issue was discovered in Octopus Deploy through 2020.4.4. If enabled, the websocket endpoint may allow an untrusted tentacle host to present itself as a trusted one.
In Octopus Deploy 3.1.0 to 2020.4.0, certain scripts can reveal sensitive information to the user in the task logs.
In Octopus Deploy 2020.3.x before 2020.3.4 and 2020.4.x before 2020.4.1, if an authenticated user creates a deployment or runbook process using Azure steps and sets the step's execution location to run on the server/worker, then (under certain circumstances) the account password...
See a CVE that affects your fleet? Push the patched version to Intune in one click with Pckgr - automated patching is the only way to keep up.
More from Octopus Deploy Pty. Ltd. or browse public.