Parameterized Trigger Plugin up to 2.43 on Jenkins file information disclosure

Summaryinfo

A vulnerability described as problematic has been identified in Parameterized Trigger Plugin up to 2.43 on Jenkins. This affects an unknown part. The manipulation results in file information disclosure. This vulnerability is identified as CVE-2022-27195. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Parameterized Trigger Plugin up to 2.43 on Jenkins (Jenkins Plugin). Affected is an unknown code block. The manipulation with an unknown input leads to a file information disclosure vulnerability. CWE is classifying the issue as CWE-538. The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. This is going to have an impact on confidentiality.

The weakness was released 03/16/2022. The advisory is available at jenkins.io. This vulnerability is traded as CVE-2022-27195 since 03/15/2022. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1083 by the MITRE ATT&CK project.

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Jenkins Plugin

Name

• Parameterized Trigger 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
• 2.29
• 2.30
• 2.31
• 2.32
• 2.33
• 2.34
• 2.35
• 2.36
• 2.37
• 2.38
• 2.39
• 2.40
• 2.41
• 2.42
• 2.43

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion