CVE-2019-15507
First published: Fri Aug 23 2019(Updated: )
In Octopus Deploy versions 2018.8.4 to 2019.7.6, when a web request proxy is configured, an authenticated user (in certain limited special-characters circumstances) could trigger a deployment that writes the web request proxy password to the deployment log in cleartext. This is fixed in 2019.7.7. The fix was back-ported to LTS 2019.6.7 as well as LTS 2019.3.8.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Octopus Deploy | >=2018.8.4<=2019.7.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-15507?
CVE-2019-15507 has a medium severity rating due to the potential exposure of sensitive information.
How do I fix CVE-2019-15507?
To fix CVE-2019-15507, upgrade to Octopus Deploy version 2019.7.7 or later.
What types of characters trigger the vulnerability in CVE-2019-15507?
The vulnerability in CVE-2019-15507 is triggered by certain limited special characters in the proxy password.
Who is affected by CVE-2019-15507?
CVE-2019-15507 affects authenticated users of Octopus Deploy versions 2018.8.4 to 2019.7.6 configured with a web request proxy.
What data is exposed in CVE-2019-15507?
CVE-2019-15507 exposes the web request proxy password in cleartext in the deployment log.
- agent/weakness
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/references
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- agent/source
- vendor/octopus
- canonical/octopus deploy
- version/octopus deploy/2018.8.4
- version/octopus deploy/2019.7.6