CVE-2018-1000057

Jenkins Credentials Binding plugin allows specifying passwords and other secrets as environment variables, and will hide them from console output in builds.

However, since Jenkins will try to resolve references to other environment variables in environment variables passed to a build, this can result in values other than the one specified being provided to a build. For example, the value p4$$w0rd would result in Jenkins passing on p4$w0rd, as $$ is the escape sequence for a single $.

Credentials Binding plugin does not prevent such a transformed value (e.g. p4$w0rd) from being shown on the build log, allowing users to reconstruct the actual password value from the transformed one.

Credentials Binding plugin will now escape any $ characters in password values so they are correctly passed to the build.

This issue did apply to freestyle and other classic job types, but does not apply to Pipelines.

CVE-2018-1000057 has a CVSS score of 4.3 (Medium). The vector is network-reachable, 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.15); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2018-1000057? CVE-2018-1000057 is a medium-severity security vulnerability in org.jenkins-ci.plugins:credentials-binding (maven), affecting versions < 1.15. It is fixed in 1.15.
2. How severe is CVE-2018-1000057? CVE-2018-1000057 has a CVSS score of 4.3 (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.
3. Which versions of org.jenkins-ci.plugins:credentials-binding are affected by CVE-2018-1000057? org.jenkins-ci.plugins:credentials-binding (maven) versions < 1.15 is affected.
4. Is there a fix for CVE-2018-1000057? Yes. CVE-2018-1000057 is fixed in 1.15. Upgrade to this version or later.
5. Is CVE-2018-1000057 exploitable, and should I be worried? Whether CVE-2018-1000057 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
6. What actually determines whether CVE-2018-1000057 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.
7. How do I fix CVE-2018-1000057? Upgrade org.jenkins-ci.plugins:credentials-binding to 1.15 or later.