Summary
This update for log4j fixes the following issue:
- Previously published fixes for log4jshell turned out to be incomplete.
Upstream has followed up on the original patch for CVE-2021-44228 with
several additional changes (LOG4J2-3198, LOG4J2-3201, LOG4J2-3208, and
LOG4J2-3211) that are included in this update. Since the totality of
those patches is pretty much equivalent to an update to the latest
version of log4j, we did update the package's tarball from version
2.13.0 to 2.16.0 instead of trying to apply those patches to the old
version. This change brings in a new dependency on 'jakarta-servlet'
and a version update of 'disruptor'. [bsc#1193743, CVE-2021-45046]
This update was imported from SUSE:SLE-15-SP2:Update.
Fixed packages 3
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.2 | disruptor | 3.4.4-lp152.2.3.1 |
| openSUSE · Leap 15.2 | jakarta-servlet | 5.0.0-lp152.2.1 |
| openSUSE · Leap 15.2 | log4j | 2.16.0-lp152.3.9.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