CVE-2019-15508
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Octopus Tentacle versions 3.0.8 to 5.0.0, when a web request proxy is configured, an authenticated user (in certain limited OctopusPrintVariables circumstances) could trigger a deployment that writes the web request proxy password to the deployment log in cleartext. This is fixed in 5.0.1. The fix was back-ported to 4.0.7.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOctopus Tentacle versions 3.0.8 through 5.0.0 contain a cleartext password storage vulnerability where web request proxy passwords are written in cleartext to deployment logs when certain OctopusPrintVariables conditions are met and a deployment is triggered by an authenticated user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0.8, <= 2019.7.6>= 3.0.8, <= 5.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Octopus Tentacle versionRun 'Tentacle --version' or check the tentacle installation directory for version information. Compare the installed version to the affected range 3.0.8 through 5.0.0.Affected if Installed version is 3.0.8, 3.0.9, 3.0.10, 3.0.11, 3.0.12, 3.0.13, 3.0.14, 3.0.15, 3.0.16, 3.0.17, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.8, 3.2.9, 3.2.10, 3.2.11, 3.2.12, 3.2.13, 3.2.14, 3.2.15, 3.2.16, 3.2.17, 3.2.18, 3.2.19, 3.2.20, 3.2.21, 3.2.22,
-
Check Octopus Server versionRun 'Octopus.Server --version' or check the server installation for version information. Compare the installed version to the affected range 3.0.8 through 2019.7.6.Affected if Installed version is between 3.0.8 and 2019.7.6 inclusive.
-
Inspect deployment logs for cleartext proxy passwordsSearch deployment log files for patterns that may indicate proxy passwords. Look for log entries containing proxy configuration with password fields in cleartext, particularly around OctopusPrintVariables output. Check the deployment logs directory (typically under the Octopus data folder) for any deployments that occurred after the Octopus installation.Affected if Deployment logs contain any web request proxy passwords written in cleartext.
-
Verify if web request proxy is configuredCheck Octopus configuration for any configured web request proxy settings. This can be done through the Octopus web portal under Infrastructure > Proxies, or by inspecting the Octopus configuration files. Look for proxy configurations that include a password field.Affected if A web request proxy is configured with a stored password, and the deployment logs have been generated with OctopusPrintVariables enabled.
-
Check for OctopusPrintVariables conditions in deploymentsReview deployment processes and variable sets to determine if OctopusPrintVariables is enabled or if conditions exist that trigger verbose variable printing during deployments. Check the deployment process steps and any custom scripting that enables verbose variable output.Affected if OctopusPrintVariables is enabled or conditions are met that cause sensitive variables including proxy passwords to be written to deployment logs.
You are affected if you are running Octopus Server 3.0.8-2019.7.6 or Octopus Tentacle 3.0.8-5.0.0, have a web request proxy with a password configured, and have deployment logs that may contain cleartext proxy passwords due to OctopusPrintVariables conditions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Octopus Tentacle to version 5.0.1 or 4.0.7 (or later), and audit existing deployment logs for any exposed proxy passwords that should be rotated and securely regenerated.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15508 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15508 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data