log4j-2.16.0-2.1 on GA media SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2024:11681-1 Final 1 1 2024-06-15T00:00:00Z current 2024-06-15T00:00:00Z 2024-06-15T00:00:00Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z log4j-2.16.0-2.1 on GA media These are all security issues fixed in the log4j-2.16.0-2.1 package on the GA media of openSUSE Tumbleweed. The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). openSUSE-Tumbleweed-2024-11681 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/security/rating/ SUSE Security Ratings https://www.suse.com/security/cve/CVE-2021-4104/ SUSE CVE CVE-2021-4104 page https://www.suse.com/security/cve/CVE-2021-45046/ SUSE CVE CVE-2021-45046 page openSUSE Tumbleweed log4j-2.16.0-2.1 log4j-javadoc-2.16.0-2.1 log4j-jcl-2.16.0-2.1 log4j-slf4j-2.16.0-2.1 log4j-2.16.0-2.1 as a component of openSUSE Tumbleweed log4j-javadoc-2.16.0-2.1 as a component of openSUSE Tumbleweed log4j-jcl-2.16.0-2.1 as a component of openSUSE Tumbleweed log4j-slf4j-2.16.0-2.1 as a component of openSUSE Tumbleweed JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. 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. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. CVE-2021-4104 openSUSE Tumbleweed:log4j-2.16.0-2.1 openSUSE Tumbleweed:log4j-javadoc-2.16.0-2.1 openSUSE Tumbleweed:log4j-jcl-2.16.0-2.1 openSUSE Tumbleweed:log4j-slf4j-2.16.0-2.1 moderate 6 AV:N/AC:M/Au:S/C:P/I:P/A:P To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2021-4104.html CVE-2021-4104 https://bugzilla.suse.com/1193662 SUSE Bug 1193662 https://bugzilla.suse.com/1193978 SUSE Bug 1193978 https://bugzilla.suse.com/1194016 SUSE Bug 1194016 https://bugzilla.suse.com/1194842 SUSE Bug 1194842 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 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, $${ctx:loginId}) 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. 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. CVE-2021-45046 openSUSE Tumbleweed:log4j-2.16.0-2.1 openSUSE Tumbleweed:log4j-javadoc-2.16.0-2.1 openSUSE Tumbleweed:log4j-jcl-2.16.0-2.1 openSUSE Tumbleweed:log4j-slf4j-2.16.0-2.1 important 5.1 AV:N/AC:H/Au:N/C:P/I:P/A:P To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2021-45046.html CVE-2021-45046 https://bugzilla.suse.com/1193743 SUSE Bug 1193743