Violation Comments to GitLab Plugin up to 2.28 on Jenkins config.xml Credentials cleartext storage

Summaryinfo

A vulnerability was found in Violation Comments to GitLab Plugin up to 2.28 on Jenkins. It has been classified as problematic. The affected element is an unknown function of the file config.xml. Performing a manipulation results in cleartext storage (Credentials). This vulnerability was named CVE-2019-10416. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Violation Comments to GitLab Plugin up to 2.28 on Jenkins (Bug Tracking Software). This affects an unknown code block of the file config.xml. The manipulation with an unknown input leads to a cleartext storage vulnerability (Credentials). CWE is classifying the issue as CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. This is going to have an impact on confidentiality. The summary by CVE is:

Jenkins Violation Comments to GitLab Plugin 2.28 and earlier stored credentials unencrypted in job config.xml files on the Jenkins master where they could be viewed by users with Extended Read permission, or access to the master file system.

The weakness was presented 09/25/2019 (oss-sec). It is possible to read the advisory at openwall.com. This vulnerability is uniquely identified as CVE-2019-10416 since 03/29/2019. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1555 according to MITRE ATT&CK.

By approaching the search of inurl:config.xml it is possible to find vulnerable targets with Google Hacking.

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

See VDB-142188, VDB-142189, VDB-142190 and VDB-142191 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Bug Tracking Software

Name

• Violation Comments to GitLab Plugin

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28

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