Skip to main content

Deserialization of Untrusted Data

CVE-2023-34050

Medium
4.3/10

Summary

In spring AMQP, it allowed list patterns for deserializable class names to be added to restrict the deserialization of data in messages from untrusted sources. However, by default, if no allowed list is provided, all classes can be deserialized. Specifically, an application is vulnerable if the "SimpleMessageConverter" or "SerializerMessageConverter" is used, the user does not configure allowed list patterns, and untrusted message originators gain permission to write messages to the RabbitMQ broker to send malicious content. This vulnerability affects org.springframework.amqp:spring-amqp package versions 1.0.0.RELEASE through 2.4.16, 3.0.0-M1 through 3.0.9, and 3.1.0-M1.

  • LOW
  • NETWORK
  • LOW
  • UNCHANGED
  • NONE
  • LOW
  • NONE
  • NONE

CWE-502 - Deserialization of Untrusted Data

Deserialization of untrusted data vulnerabilities enable an attacker to replace or manipulate a serialized object, replacing it with malicious data. When the object is deserialized at the victim's end the malicious data is able to compromise the victim’s system. The exploit can be devastating, its impact may range from privilege escalation, broken access control, or denial of service attacks to allowing unauthorized access to the application's internal code and logic which can compromise the entire system.

References

Advisory Timeline

  • Published