Deserialization of Untrusted Data The advisory has been revoked - it doesn't affect any version of package log4j-jcl  (opens in a new tab)


Threat Intelligence

EPSS
0.06% (27th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS9-LOG4JJCL-6037712
  • published27 Oct 2023
  • disclosed19 Oct 2023

Introduced: 19 Oct 2023

CVE-2023-34050  (opens in a new tab)
CWE-502  (opens in a new tab)

Amendment

The Centos security team deemed this advisory irrelevant for Centos:9.

NVD Description

Note: Versions mentioned in the description apply only to the upstream log4j-jcl package and not the log4j-jcl package as distributed by Centos.

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