CVE-2018-11320
First published: Mon May 21 2018(Updated: )
In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the target do not have sensitive values obfuscated in the deployment logs.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Octopus Deploy | >=2018.4.4<=2018.5.1 |
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-2018-11320?
CVE-2018-11320 is classified as a medium severity vulnerability.
How do I fix CVE-2018-11320?
To fix CVE-2018-11320, upgrade Octopus Deploy to version 2018.6.0 or later.
What is the main issue with CVE-2018-11320?
The main issue with CVE-2018-11320 is that sensitive variable values are not obfuscated in deployment logs.
Which versions of Octopus Deploy are affected by CVE-2018-11320?
CVE-2018-11320 affects Octopus Deploy versions from 2018.4.4 to 2018.5.1.
What are the implications of CVE-2018-11320 for users?
Users of Octopus Deploy may inadvertently expose sensitive information through deployment logs due to CVE-2018-11320.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/author
- agent/severity
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/octopus
- canonical/octopus deploy
- version/octopus deploy/2018.4.4
- version/octopus deploy/2018.5.1