Deserialization of Untrusted Data The advisory has been revoked - it doesn't affect any version of package org.apache.logging.log4j-log4j (opens in a new tab)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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 IDSNYK-RHEL9-ORGAPACHELOGGINGLOG4JLOG4J-6037691
- published27 Oct 2023
- disclosed19 Oct 2023
Introduced: 19 Oct 2023
CVE-2023-34050 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:9.
NVD Description
Note: Versions mentioned in the description apply only to the upstream org.apache.logging.log4j-log4j package and not the org.apache.logging.log4j-log4j package as distributed by RHEL.
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