OctopusdeployApplication · Jenkins
CVE-2019-1003071
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 · uneditedJenkins OctopusDeploy Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system.
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 confidenceThe Jenkins OctopusDeploy Plugin stores credentials unencrypted in its global configuration file on the Jenkins master. Users with access to the master file system can view these plaintext credentials, exposing sensitive authentication material.
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
OctopusdeployApplication
all versionsCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify OctopusDeploy plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'OctopusDeploy' or check the $JENKINS_HOME/plugins/ directory for the octupusdeploy plugin folderAffected if The plugin is listed as installed and active in Jenkins
-
Locate the plugin's global configuration fileLook for the OctopusDeploy plugin configuration in $JENKINS_HOME/org.jenkinsci.plugins.octopusdeploy.Config.xml or inspect the main $JENKINS_HOME/config.xml for an <org.jenkinsci.plugins.octopusdeploy> sectionAffected if A configuration file exists for the OctopusDeploy plugin in the Jenkins home directory
-
Inspect configuration for stored credentialsOpen the plugin's configuration file and search for credential fields such as 'apiKey', 'password', 'secret', or 'credentials' entriesAffected if The configuration file contains any credential-related fields with values present (not empty)
-
Determine if credentials are encryptedExamine the credential values in the configuration file: encrypted values typically appear as long alphanumeric strings with base64 encoding or Jenkins-specific encrypted format, while plaintext credentials appear as readable textAffected if Credential values appear as readable plain text rather than encrypted strings, or the configuration uses plaintext storage format without Jenkins credential binding
A user is affected if the OctopusDeploy plugin is installed, has been configured with credentials, and those credentials are stored in plaintext (unencrypted) form in the plugin's configuration file accessible on the Jenkins master filesystem.
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 to a plugin version that encrypts credentials or migrate credentials to Jenkins' built-in credential store. Restrict filesystem access to the Jenkins master directory.
Fix this in Octopusdeploy
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003071 — 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-1003071 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