First published: Wed May 06 2020(Updated: )
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).
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.jenkins-ci.plugins:ec2 | <=1.50.1 | 1.50.2 |
Jenkins Amazon Ec2 | <=1.50.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2020-2187 is medium.
Jenkins Amazon EC2 Plugin 1.50.1 and earlier unconditionally accepts self-signed HTTPS certificates.
No, Jenkins Amazon EC2 Plugin 1.50.1 and earlier does not perform hostname validation when connecting to Windows agents.
The lack of validation in Jenkins Amazon EC2 Plugin 1.50.1 and earlier could be abused through a man-in-the-middle attack.
To fix CVE-2020-2187, update to version 1.50.2 of Jenkins Amazon EC2 Plugin or later.