DeployApplication · Jenkins
CVE-2017-1000113
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 · uneditedThe Deploy to container Plugin stored passwords unencrypted as part of its configuration. This allowed users with Jenkins master local file system access, or users with Extended Read access to the jobs it is used in, to retrieve those passwords. The Deploy to container Plugin now integrates with Credentials Plugin to store passwords securely, and automatically migrates existing passwords.
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 Deploy to container Plugin stored deployment passwords in plaintext within its configuration files on the Jenkins master. Users with local filesystem access or Extended Read permissions to the affected jobs could retrieve these unencrypted passwords, leading to credential exposure.
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
DeployApplication
<= 1.12CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/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 if Deploy to container Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Deploy to container' plugin, or check the plugin directory (typically $JENKINS_HOME/plugins/deploy/*.jpi)Affected if Plugin is present and version is 1.12 or lower
-
Identify jobs using Deploy to container PluginSearch job config.xml files for the presence of '<hudson.tasks.DeployPublisher>' or similar deployment publisher elements in $JENKINS_HOME/jobs/*/config.xmlAffected if Jobs contain DeployPublisher configuration sections
-
Inspect job configurations for plaintext passwordsOpen the config.xml file of a job using the plugin and look for password-related fields (such as passwords, credentials, or keystore passwords) that appear as plaintext values rather than masked or referencing the Credentials PluginAffected if Password fields contain unmasked, plaintext string values instead of credential IDs or encrypted references
-
Verify credentials storage mechanismCheck if the plugin configuration references credentials via <credentialsId> elements pointing to the Jenkins Credentials Plugin, or if passwords are stored directly as plain text in elements like <password> or similarAffected if Passwords are stored directly as plain text values rather than as credential ID references
A user is affected if the Deploy to container Plugin version 1.12 or lower is installed AND job configurations contain deployment passwords stored as plaintext rather than as references to the Jenkins Credentials Plugin.
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 the Deploy to container Plugin to the version that integrates with Jenkins Credentials Plugin for secure password storage, and verify that existing passwords were automatically migrated. Revoke or rotate any passwords that may have been exposed prior to the update.
Fix this in Deploy
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000113 — 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-2017-1000113 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