This vulnerability in Spring AMQP arises when applications configure their broker connection URI with the amqps scheme but omit calling setUseSSL(true). In this scenario, TLS encryption is established; however, the implementation does not perform certificate validation or hostname verification, effectively negating the security benefits of TLS. Affected versions include 2.4.0 through 2.4.17, 3.1.0 through 3.1.15, 3.2.0 through 3.2.10, and 4.0.0 through 4.0.3. The vulnerability is classified under CWE-295 (Improper Certificate Validation). No official patch or remediation level has been provided as of the published date.

The vulnerability allows TLS connections to be established without verifying the server's certificate or hostname, which can enable man-in-the-middle attacks or connections to untrusted brokers. The confidentiality of the connection is partially protected by TLS encryption, but the lack of validation undermines trust in the connection endpoint. The CVSS score of 4.0 reflects a medium impact primarily on confidentiality, with no direct impact on integrity or availability reported.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, ensure that applications explicitly call setUseSSL(true) when configuring RabbitConnectionFactoryBean with an amqps URI to enable proper certificate validation and hostname verification. Avoid relying solely on setUri("amqps://...") without this additional configuration.