![]() ![]() Apache Log4j 1.2 reached end of life in August 2015. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. ![]() Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.Ĥ Apache, Fedoraproject, Oracle and 1 moreĤ6 Log4j, Fedora, Advanced Supply Chain Planning and 43 more This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $$) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.Ħ Apache, Debian, Fedoraproject and 3 moreĦ1 Log4j, Debian Linux, Fedora and 58 more This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. 121 Log4j, Debian Linux, Cloud Manager and 118 moreĪpache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |