JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results
Feedback