Aller au contenu
en Se connecter
5.0 Moyenne

CVE-2023-34050 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…

Description

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

Produits et versions touchés

Produit Versions touchées Corrigé en
Spring AMQP 3.0 3.0.0 → < 3.0.10 3.0.10
Spring AMQP 1.0 1.0.0 → < 2.4.17 2.4.17

Références

Chronologie

  1. Publiée
  2. Dernière modification

Autres CVE de Spring AMQP

Les 8 CVE de Spring AMQP →
CVE-2026-59320 When a container-level ErrorHandler is configured (the mitigation for finding 221000), each delivery whose processing… 6.5 Moyenne CVE-2026-59272 Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is… 6.8 Moyenne CVE-2026-59275 A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener thread —… 6.6 Moyenne CVE-2026-59271 When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext in the thrown… 5.3 Moyenne
Suivre cette CVE