Summary
This update for log4j fixes the following issue:
CVE-2021-44228: The previously published fix by upstream turned out to be
incomplete. Therefore, upstream has recommended disabling JNDI support in log4j
by default to be completely sure that this vulnerability cannot be exploited.
This update implements that recommendation and disables JNDI support by
default. [bsc#1193611, CVE-2021-44228]
CVE-2021-45046: A Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack
is also fixed by disabling JNDI support by default (bsc#1193743)
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.3 | log4j | 2.13.0-4.6.1 |
Vulnerabilities 2
-
Critical 10.0
Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who …
KEV Dec 10, 2021 -
Critical 9.0
Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack
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-defaul…
KEV May 1, 2023