Spring AMQP’s sendAndReceive() uses a fixed reply queue and assigns correlation IDs by incrementing a simple counter. Because the counter is predictable, an attacker can guess the expected correlation ID for a reply, enabling them to send a forged response that will be accepted by the consumer. This type of reply poisoning can cause the application to process incorrect data or perform unintended actions, potentially leading to loss of confidentiality or integrity. The vulnerability is classified as CWE‑330, the use of an insecure, predictable random number generator.

The flaw exists in Spring AMQP 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. Any deployment using these versions and relying on sendAndReceive() over a fixed reply queue is affected.

The CVSS score of 4.4 indicates low overall severity, and the EPSS score is currently not available, implying that the likelihood of exploitation has not been quantified. The vulnerability is not listed in the CISA KEV catalog. Exploitation would require an attacker with the ability to send messages to the affected RabbitMQ broker or to have network access to the AMQP client, so the attack vector is inferred to be either local network or remote depending on the broker’s exposure. No specific exploit code has been published, but the predictable IDs provide a clear attack path for an actor with sufficient network or application access.