In Spring AMQP sequential correlation IDs enable reply poisoning on fixed reply queues
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 |
|
|
Correlation IDs for replies in the RabbitTemplate.sendAndReceive() with the fixed reply queue are predictable due to internal simple counter.
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 uses predictable reply correlation IDs in RabbitTemplate.sendAndReceive() when configured with a fixed reply queue, because it generates them with a simple counter. An attacker can predict those IDs; the input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Teams running 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 should check their use of fixed reply queues.