Credentials Binding Plugin up to 1.14 on Jenkins Log Password credentials management

Summaryinfo

A vulnerability was found in Credentials Binding Plugin up to 1.14 on Jenkins. It has been classified as problematic. The affected element is an unknown function of the component Log Handler. Performing a manipulation results in credentials management (Password). This vulnerability is reported as CVE-2018-1000057. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Credentials Binding Plugin up to 1.14 on Jenkins (Jenkins Plugin). This affects an unknown code block of the component Log Handler. The manipulation with an unknown input leads to a credentials management vulnerability (Password). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The bug was discovered 02/05/2018. The weakness was disclosed 02/09/2018 (Website). The advisory is shared at jenkins.io. This vulnerability is uniquely identified as CVE-2018-1000057 since 02/05/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-113094, VDB-113095, VDB-113096 and VDB-113098 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Jenkins Plugin

Name

• Credentials Binding Plugin

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion