CVE-2018-1000057: Medium severity jenkins credentials binding vulnerability
Jenkins Credentials Binding Plugin 1.14 and earlier masks passwords it provides to build processes in their build logs. Jenkins however transforms provided password values, e.g. replacing environment variable references, which could result in values different from but similar to configured passwords being provided to the build. Those values are not subject to masking, and could allow unauthorized users to recover the original password.
Other sources
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2018-1000057?
CVE-2018-1000057 is classified as a medium severity vulnerability.
How do I fix CVE-2018-1000057?
To fix CVE-2018-1000057, upgrade the Jenkins Credentials Binding Plugin to version 1.15 or later.
Which versions of Jenkins Credentials Binding Plugin are affected by CVE-2018-1000057?
Versions 1.14 and earlier of the Jenkins Credentials Binding Plugin are affected by CVE-2018-1000057.
What type of information is compromised in CVE-2018-1000057?
CVE-2018-1000057 compromises the masking of passwords in build logs, potentially exposing sensitive information.
Is CVE-2018-1000057 a code execution vulnerability?
No, CVE-2018-1000057 does not directly lead to code execution but affects the confidentiality of sensitive information.