Lack of SSL/TLS certificate and hostname validation in Amazon EC2 Plugin
Date: 2022-05
Affected: maven/org.jenkins-ci.plugins:ec2
Attack vector: deserialization
Category: vulnerability-disclosure
Severity: High
CVE: CVE-2020-2185
CVE-2020-2187
CVE-2020-2189
CWE: CWE-295
CWE-300
CWE-502
CVSS: 5.6 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L)

Amazon EC2 Plugin connects to Windows agents via HTTPS. Amazon EC2 Plugin 1.50.1 and earlier unconditionally accepts self-signed HTTPS certificates and does not perform hostname validation when connecting to Windows agents. This lack of validation could be abused using a man-in-the-middle attack to intercept these connections to build agents. Amazon EC2 Plugin 1.50.2 by default no longer accepts self-signed HTTPS certificates and performs hostname validation. A new configuration option allows restoring the previous, unsafe behavior. For more information see [the plugin documentation](https://github.com/jenkinsci/ec2-plugin/#securing-the-connection-to-windows-amis).


Mitigations:

Architectural layers (MAESTRO):