Credentials Binding Plugin up to 1.22 on Jenkins insufficiently protected credentials

Summaryinfo

A vulnerability has been found in Credentials Binding Plugin up to 1.22 on Jenkins and classified as problematic. The affected element is an unknown function. The manipulation leads to insufficiently protected credentials. This vulnerability is uniquely identified as CVE-2020-2182. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Credentials Binding Plugin up to 1.22 on Jenkins (Jenkins Plugin) and classified as problematic. This issue affects an unknown part. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. Using CWE to declare the problem leads to CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. Impacted is confidentiality. The summary by CVE is:

Jenkins Credentials Binding Plugin 1.22 and earlier does not mask (i.e., replace with asterisks) secrets containing a `$` character in some circumstances.

The weakness was disclosed 05/06/2020 (oss-sec). It is possible to read the advisory at openwall.com. The identification of this vulnerability is CVE-2020-2182 since 12/05/2019. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is necessary for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.

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

The entries VDB-154786, VDB-154788, VDB-154789 and VDB-154790 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for 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
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion