Configuration as Code Plugin up to 1.26 on Jenkins Incomplete Fix CVE-2019-10343 Log log file

Summaryinfo

A vulnerability classified as problematic has been found in Configuration as Code Plugin up to 1.26 on Jenkins. This impacts an unknown function of the component Incomplete Fix CVE-2019-10343. This manipulation causes log file (Log). This vulnerability is handled as CVE-2019-10367. It is possible to launch the attack on the local host. There is not any exploit available.

Detailsinfo

A vulnerability has been found in Configuration as Code Plugin up to 1.26 on Jenkins (Jenkins Plugin) and classified as problematic. Affected by this vulnerability is some unknown processing of the component Incomplete Fix CVE-2019-10343. The manipulation with an unknown input leads to a log file vulnerability (Log). The CWE definition for the vulnerability is CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. As an impact it is known to affect confidentiality. The summary by CVE is:

Due to an incomplete fix of CVE-2019-10343, Jenkins Configuration as Code Plugin 1.26 and earlier did not properly apply masking to some values expected to be hidden when logging the configuration being applied.

The weakness was released 08/07/2019 (Website). The advisory is shared at openwall.com. This vulnerability is known as CVE-2019-10367 since 03/29/2019. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

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

Entries connected to this vulnerability are available at VDB-139632, VDB-139624, VDB-139625 and VDB-139626. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Jenkins Plugin

Name

• Configuration as Code 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
• 1.23
• 1.24
• 1.25
• 1.26

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion