Описание
In spring AMQP versions 1.0.0 to 2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable class names were added to Spring AMQP, allowing users to lock down deserialization of data in messages from untrusted sources; however by default, when no allowed list was provided, all classes could be deserialized. Specifically, an application is vulnerable if
- the SimpleMessageConverter or SerializerMessageConverter is used
- the user does not configure allowed list patterns
- untrusted
message originators gain permissions to write messages to the RabbitMQ
broker to send malicious content
A flaw was found in Spring Framework AMQP. An allowed list exists in Spring AMQP, but when no allowed list is provided, all classes could be deserialized, allowing a malicious user to send harmful content to the broker.
Отчет
This flaw requires previous knowledge and access to the messages in order to get them deserialized and possibly leak information. It also requires missing server side configurations to prevent unwanted behavior. Therefore, this is rated as a Moderate impact.
Меры по смягчению последствий
An application may be vulnerable if:
- The SimpleMessageConverter or SerializerMessageConverter is used
- The user does not configure allowed list patterns
- Untrusted message originators gain permissions to write messages to the RabbitMQ broker to send malicious content Make sure these are avoided in order to mitigate the issue.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| A-MQ Clients 2 | org.amqphub.spring-amqp-10-jms-spring-boot-parent | Affected | ||
| A-MQ Clients 2 | org.apache.logging.log4j-log4j | Not affected | ||
| Red Hat build of Apache Camel for Spring Boot 3 | spring-amqp | Will not fix | ||
| Red Hat Enterprise Linux 9 | log4j | Not affected | ||
| AMQ Clients | org.amqphub.spring-amqp-10-jms-spring-boot-parent | Fixed | RHSA-2023:7697 | 07.12.2023 |
Показывать по
Дополнительная информация
Статус:
EPSS
4.3 Medium
CVSS3
Связанные уязвимости
In spring AMQP versions 1.0.0 to 2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable class names were added to Spring AMQP, allowing users to lock down deserialization of data in messages from untrusted sources; however by default, when no allowed list was provided, all classes could be deserialized. Specifically, an application is vulnerable if * the SimpleMessageConverter or SerializerMessageConverter is used * the user does not configure allowed list patterns * untrusted message originators gain permissions to write messages to the RabbitMQ broker to send malicious content
In spring AMQP versions 1.0.0 to 2.4.16 and 3.0.0 to 3.0.9 , allowed list patterns for deserializable class names were added to Spring AMQP, allowing users to lock down deserialization of data in messages from untrusted sources; however by default, when no allowed list was provided, all classes could be deserialized. Specifically, an application is vulnerable if * the SimpleMessageConverter or SerializerMessageConverter is used * the user does not configure allowed list patterns * untrusted message originators gain permissions to write messages to the RabbitMQ broker to send malicious content
Уязвимость приложения для обмена сообщениями Spring AMQP RabbitMQ, связанная с недостатками механизма десериализации, позволяющая нарушителю получить несанкционированный доступ на запись сообщений в RabbitMQ
EPSS
4.3 Medium
CVSS3