In Spring AMQP the RabbitConnectionFactoryBean.setUri("amqps://...") bypasses secure SSL setup, uses TrustEverythingTrustManager
Spring AMQP
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.amqp:spring-amqp Maven |
|
|
Spring AMQP
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.amqp:spring-amqp Maven |
|
|
Applications that configure their broker connection via RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(true) get TLS encryption with no certificate validation and no hostname verification.
Affected versions: Spring AMQP 4.0.0 through 4.0.3; 3.2.0 through 3.2.10; 3.1.0 through 3.1.15; 2.4.0 through 2.4.17.
From the CVE record · vmware
Spring AMQP applications that configure a broker with RabbitConnectionFactoryBean.setUri("amqps://...") without also calling setUseSSL(true) use TLS without certificate or hostname verification. An attacker able to intercept the broker connection could impersonate the broker; the issue depends on that configuration, not user interaction.
Check applications using Spring AMQP 4.0.0–4.0.3, 3.2.0–3.2.10, 3.1.0–3.1.15, or 2.4.0–2.4.17.