Pipeline: AWS Steps Plugin up to 1.40 on Jenkins YAML Parser deserialization

Summaryinfo

A vulnerability, which was classified as critical, has been found in Pipeline: AWS Steps Plugin up to 1.40 on Jenkins. This impacts an unknown function of the component YAML Parser. This manipulation causes deserialization. This vulnerability appears as CVE-2020-2166. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in Pipeline: AWS Steps Plugin up to 1.40 on Jenkins (Jenkins Plugin) and classified as critical. Affected by this vulnerability is an unknown functionality of the component YAML Parser. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Jenkins Pipeline: AWS Steps Plugin 1.40 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types, resulting in a remote code execution vulnerability.

The weakness was presented 03/25/2020 (oss-sec). The advisory is shared at openwall.com. This vulnerability is known as CVE-2020-2166 since 12/05/2019. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation needs a single authentication. Neither technical details nor an exploit are publicly available.

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

See VDB-152287, VDB-152288, VDB-152289 and VDB-152290 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Jenkins Plugin

Name

• Pipeline: AWS Steps 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
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40

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