Advisories for Maven/Org.jenkins-Ci.plugins/Ec2 package

Jenkins Amazon EC2 Plugin 1.43 and earlier wrote the beginning of private keys to the Jenkins system log.

Users with permission to create or configure agents in Jenkins 1.37 and earlier could configure an EC2 agent to run arbitrary shell commands on the master node whenever the agent was supposed to be launched. Configuration of these agents now requires the 'Run Scripts' permission typically only granted to administrators.

A missing permission check in Jenkins Amazon EC2 Plugin form-related methods allows users with Overall/Read access to enumerate credential IDs of the credentials stored in Jenkins.

Jenkins Amazon EC2 Plugin unconditionally accepts self-signed certificates and does not perform hostname validation, enabling man-in-the-middle attacks.

A cross-site request forgery vulnerability in Jenkins Amazon EC2 Plugin allows attackers to provision instances.

Jenkins Amazon EC2 Plugin does not validate SSH host keys when connecting agents, enabling man-in-the-middle attacks.

A missing permission check in Jenkins Amazon EC2 Plugin 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.

A cross-site request forgery vulnerability in Jenkins Amazon EC2 Plugin allows attackers to connect to an attacker-specified URL within the AWS region using attacker-specified credentials IDs obtained through another method.