VMware offers training and certification to turbo-charge your progress.Learn more
spring-amqp, 1.x versions prior to 1.7.10, 2.x versions prior to 2.0.6 expose a man-in-the middle vulnerability.
The Spring RabbitMQ Java Client does not perform hostname validation.
This means that SSL certificates of other hosts are blindly accepted as long as they are trusted.
To exploit this vulnerability an attacker has to perform a man-in-the-middle (MITM) attack between a Java application using the Spring RabbitMQ Java Client and an RabbitMQ server it's connecting to.
TLS normally protects users and systems against MITM attacks, it cannot if certificates from other trusted hosts are accepted by the client.
Spring AMQP uses the RabbitMQ amqp-client java library for communication with RabbitMQ.
It uses the RabbitConnectionFactoryBean to create/configure the connection factory.
Users of affected versions should apply the following mitigation:
This issue was identified and responsibly reported by Peter Stöckli of Alphabot Security, Switzerland.
The VMware Security Response team provides a single point of contact for the reporting of security vulnerabilities in VMware Tanzu products and coordinates the process of investigating any reported vulnerabilities.
To report a security vulnerability in a VMware service or product please refer to the VMware Security Response Policy.