Spring AMQP clients that call RabbitConnectionFactoryBean.setUri('amqps://...') without also enabling SSL through setUseSSL(true) establish TLS connections that bypass certificate validation and hostname verification, using a TrustEverythingTrustManager. Based on the description, this flaw allows an attacker on the network path to inject or eavesdrop on broker traffic, potentially exposing credentials, messages, and sensitive data without the client recognizing the misconfiguration. The weakness is a classic example of insecure configuration leading to loss of confidentiality and integrity of data in transit.

Spring: Spring AMQP versions 4.0.0 through 4.0.3, 3.2.0 through 3.2.10, 3.1.0 through 3.1.15, and 2.4.0 through 2.4.17 are affected. These include all builds released within those version ranges.

The CVSS score is 4, reflecting low to moderate risk. The EPSS score is not available, and KEV does not list this vulnerability, suggesting it is not a widely exploited threat yet. Based on the description, an attacker positioned between the client and broker could exploit the insecure TLS settings. Because the flaw is a configuration oversight, applying updates mitigates the risk.