Loading vulnerability…
CVE-2018-18850 affects Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1. An authenticated user who has permission to modify deployment processes can upload a maliciously crafted YAML configuration. Processing of that YAML can lead to remote execution of arbitrary code on the Octopus Server. On self-hosted installations, the code executes in the security context of the Octopus Server service, which by default is SYSTEM.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/windows/http/octopusdeploy_deploy.rb) that exploits CVE-2018-18850, a vulnerability in Octopus Deploy Server. The exploit requires valid credentials (username/password) or an API key and leverages the Octopus Deploy API to add a malicious PowerShell script step to a deployment process. The module automates authentication, project and step enumeration, step injection, release creation, and deployment, resulting in the execution of arbitrary PowerShell code on the target server. The payload is fully customizable using Metasploit's payload system, making this a weaponized exploit. The main attack vector is network-based, targeting the Octopus Deploy HTTP API endpoints. The code is written in Ruby and is structured as a standard Metasploit exploit module.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.