Amazon EC2 Plugin up to 1.47 on Jenkins Permission Check improper authorization

Summaryinfo

A vulnerability identified as critical has been detected in Amazon EC2 Plugin up to 1.47 on Jenkins. This vulnerability affects unknown code of the component Permission Check. This manipulation causes improper authorization. This vulnerability appears as CVE-2020-2091. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in Amazon EC2 Plugin up to 1.47 on Jenkins (Jenkins Plugin) and classified as critical. Affected by this vulnerability is some unknown functionality of the component Permission Check. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A missing permission check in Jenkins Amazon EC2 Plugin 1.47 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL within the AWS region using attacker-specified credentials IDs obtained through another method.

The weakness was presented 01/15/2020 (oss-sec). The advisory is shared at openwall.com. This vulnerability is known as CVE-2020-2091 since 12/05/2019. The exploitation appears to be easy. The attack can be launched remotely. A single authentication is required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-2802). See VDB-149052, VDB-149054, VDB-149055 and VDB-149056 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

• Amazon EC2 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
• 1.41
• 1.42
• 1.43
• 1.44
• 1.45
• 1.46
• 1.47

License

• commercial

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