SB2020050723 - Multiple vulnerabilities in Jenkins Amazon EC2 plugin

CSH
CYBERSECURITY HELP
Sign In REGISTER

Main Vulnerability Database SB2020050723

SB2020050723 - Multiple vulnerabilities in Jenkins Amazon EC2 plugin

Published: May 7, 2020

Security Bulletin ID SB2020050723
Severity
Medium
Patch available
YES
Number of vulnerabilities 4
Exploitation vector Remote access
Highest impact Data manipulation

Breakdown by Severity

Medium 50% Low 50%
  • Low
  • Medium
  • High
  • Critical

Description

This security bulletin contains information about 4 secuirty vulnerabilities.


1) Improper Authorization (CVE-ID: CVE-2020-2188)

The vulnerability allows a remote user to bypass authorization checks.

The vulnerability exists due to the affected plugin performs improper permission checks when providing a list of applicable credentials IDs to allow users configuring the plugin to select the one to use. A remote authenticated attacker with Overall/Read permission can get a list of valid credentials IDs.


2) Man-in-the-Middle (MitM) attack (CVE-ID: CVE-2020-2187)

The vulnerability allows a remote attacker to perform a man-in-the-middle (MitM) attack.

The vulnerability exists due to the affected plugin unconditionally accepts self-signed HTTPS certificates and does not perform hostname validation when connecting to Windows agents. A remote attacker can perform a man-in-the-middle attack and intercept these connections to build agents.


3) Cross-site request forgery (CVE-ID: CVE-2020-2186)

The vulnerability allows a remote attacker to perform cross-site request forgery attacks.

The vulnerability exists due to insufficient validation of the HTTP request origin. A remote attacker can trick the victim to visit a specially crafted web page and perform arbitrary actions on behalf of the victim on the vulnerable website.


4) Man-in-the-Middle (MitM) attack (CVE-ID: CVE-2020-2185)

The vulnerability allows a remote attacker to perform a man-in-the-middle (MitM) attack.

The vulnerability exists due to the affected plugin does not use SSH host key validation when connecting to agents. A remote attacker can perform a man-in-the-middle attack and intercept these connections to build agents.


Remediation

Install update from vendor's website.

References