Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSimpleAmqpHeaderMapper.toHeaders() first populates the Spring Messaging headers with framework-derived values from the received MessageProperties (such as amqp_receivedUserId, amqp_consumerQueue, amqp_deliveryTag and amqp_redelivered) and then copies the raw AMQP message headers, which are fully controlled by the publisher. As a result, a publisher can supply custom headers whose names collide with the amqp_* constants and silently replace the trusted values that downstream @RabbitListener handlers see via @Header or MessageHeaders.
Applications are affected if an attacker is able to publish messages routed to a listener and the application relies on an amqp_* framework header, for example AmqpHeaders.RECEIVED_USER_ID (broker-validated identity) or AmqpHeaders.CONSUMER_QUEUE, for authorization or routing decisions.
Spring AMQP:
| Fix version | Availability |
|---|---|
| 4.1.2.1 | Enterprise Support Only |
| 4.1.3 | OSS |
| 4.0.6.1 | Enterprise Support Only |
| 4.0.7 | OSS |
| 3.2.14 | Enterprise Support Only |
| 2.4.20 | Enterprise Support Only |
Users of affected versions who cannot upgrade should obtain trusted values, such as the received user id or consumer queue, directly from the MessageProperties of the received org.springframework.amqp.core.Message rather than from the mapped amqp_* Spring Messaging headers.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy