What is CVE-2017-1000113?

CVE-2017-1000113 is a medium-severity security vulnerability in org.jenkins-ci.plugins:deploy (maven), affecting versions <= 1.12. It is fixed in 1.13.

How severe is CVE-2017-1000113?

CVE-2017-1000113 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.jenkins-ci.plugins:deploy are affected by CVE-2017-1000113?

org.jenkins-ci.plugins:deploy (maven) versions <= 1.12 is affected.

Is there a fix for CVE-2017-1000113?

Yes. CVE-2017-1000113 is fixed in 1.13. Upgrade to this version or later.

Is CVE-2017-1000113 exploitable, and should I be worried?

Whether CVE-2017-1000113 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2017-1000113 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2017-1000113 in org.jenkins-ci.plugins:deploy

Q: How severe is CVE-2017-1000113?

CVE-2017-1000113 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.jenkins-ci.plugins:deploy are affected by CVE-2017-1000113?

org.jenkins-ci.plugins:deploy (maven) versions <= 1.12 is affected.

Q: Is there a fix for CVE-2017-1000113?

Yes. CVE-2017-1000113 is fixed in 1.13. Upgrade to this version or later.

Q: Is CVE-2017-1000113 exploitable, and should I be worried?

Whether CVE-2017-1000113 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2017-1000113 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2017-1000113?

Upgrade org.jenkins-ci.plugins:deploy to 1.13 or later.

Summary

Jenkins Deploy to container Plugin stored plain text passwords in job configuration

The 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.

Impact

CVE-2017-1000113 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.13); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins:deploy (<= 1.12)

Security releases

org.jenkins-ci.plugins:deploy → 1.13 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.jenkins-ci.plugins:deploy to 1.13 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2017-1000113? CVE-2017-1000113 is a medium-severity security vulnerability in org.jenkins-ci.plugins:deploy (maven), affecting versions <= 1.12. It is fixed in 1.13.
How severe is CVE-2017-1000113? CVE-2017-1000113 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.jenkins-ci.plugins:deploy are affected by CVE-2017-1000113? org.jenkins-ci.plugins:deploy (maven) versions <= 1.12 is affected.
Is there a fix for CVE-2017-1000113? Yes. CVE-2017-1000113 is fixed in 1.13. Upgrade to this version or later.
Is CVE-2017-1000113 exploitable, and should I be worried? Whether CVE-2017-1000113 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2017-1000113 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2017-1000113? Upgrade org.jenkins-ci.plugins:deploy to 1.13 or later.