dbcve.org
Octopus DeployApplication · Octopus

CVE-2019-8944

MEDIUM · 6.5 CVSS v3.0 Published 2019-02-20
Fix available
A fix is available. Upgrade to 2019.1.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An Information Exposure issue in the Terraform deployment step in Octopus Deploy before 2019.1.8 (and before 2018.10.4 LTS) allows remote authenticated users to view sensitive Terraform output variables via log files.

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 · moderate confidence

In Octopus Deploy versions prior to 2019.1.8 (and 2018.10.4 LTS), the Terraform deployment step writes sensitive output variables to log files. Authenticated users with access to these logs can read sensitive Terraform output variables that should remain confidential.

MitigationUpgrade Octopus Deploy to version 2019.1.8 or later (or 2018.10.4 LTS or later) to patch this vulnerability. Review existing log files for any exposed sensitive data and rotate any compromised credentials or secrets.

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
Octopus DeployApplication
Affected:<= 2018.9.17= 2018.10.0= 2018.10.1= 2018.10.2= 2018.10.3
Octopus ServerApplication
Affected:>= 2018.11.0, < 2019.1.8

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Octopus Deploy version
    Access the Octopus Web UI, go to the Help > About page, or run 'octo version' from the command line if available. The version is also visible in the footer of the Octopus interface.
    Affected if The version is one of: <= 2018.9.17, 2018.10.0, 2018.10.1, 2018.10.2, 2018.10.3, or >= 2018.11.0 but < 2019.1.8. Any version in these ranges is affected.
  2. Verify if Terraform deployment step exists
    In the Octopus Web UI, navigate to Projects > select a project > Process > Deployment Steps. Look for a step named 'Deploy a Terraform template' or similar Terraform-related step type.
    Affected if A Terraform deployment step has been used in any project. The vulnerability only applies when this step type is configured.
  3. Inspect task logs for exposed Terraform outputs
    Go to the Tasks or Activity log section in Octopus. Locate task logs from deployments that used the Terraform deployment step. Search within these logs for lines containing 'output' or sensitive-looking key-value pairs that resemble Terraform output variable names and values.
    Affected if Log files contain Terraform output variable names and their corresponding values in plain text. This indicates the vulnerability has been triggered.
  4. Check for sensitive variables in deployment logs
    In the project task history, open individual deployment logs. Look for any entries where Terraform output variables (typically in format 'key = value') appear in the log output, especially under sections labeled 'Terraform apply' or 'output'.
    Affected if Sensitive Terraform output variables are visible in the deployment logs. Any authenticated user with task log access can read these values.

Your Octopus Deploy instance is affected if it runs a version prior to 2019.1.8 (or 2018.10.4 LTS) AND has used the Terraform deployment step, with sensitive output variables appearing in task logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2019.1.8 or later
Fixed in 2019.1.8
Interim mitigation

Upgrade Octopus Deploy to version 2019.1.8 or later (or 2018.10.4 LTS or later) to patch this vulnerability. Review existing log files for any exposed sensitive data and rotate any compromised credentials or secrets.

Fix this in Octopus Deploy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-8944 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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