This vulnerability (CWE-295) arises from Spring Boot's RabbitMQ auto-configuration failing to verify the hostname in SSL certificates when connecting to RabbitMQ brokers. Affected versions include 3.5.0 to 3.5.13 and 4.0.0 to 4.0.5. The lack of hostname verification undermines SSL security guarantees, potentially allowing attackers to intercept or manipulate communications. The vendor has addressed this issue in Spring Boot versions 3.5.14 and 4.0.6.

The vulnerability allows an attacker with network access to perform man-in-the-middle attacks by exploiting the lack of hostname verification in SSL connections to RabbitMQ brokers. This can lead to partial confidentiality, integrity, and availability impacts as indicated by the CVSS vector (C:L/I:L/A:L). No known exploits are reported in the wild.

Upgrade affected Spring Boot versions to 3.5.14 or 4.0.6 or later, where the hostname verification issue in RabbitMQ SSL connections is fixed. Patch status is confirmed by the vendor advisory specifying these fixed versions. Until upgraded, consider alternative mitigations such as disabling SSL bundles or enforcing hostname verification through custom configuration if feasible.