Summary
This update for logback fixes the following issues:
Upgrade to version 1.2.8
+ In response to log4Shell/CVE-2021-44228, all JNDI lookup code in logback
has been disabled until further notice. This impacts
ContextJNDISelector and insertFromJNDI element in
configuration files.
+ Also in response to log4Shell/CVE-2021-44228, all database (JDBC) related
code in the project has been removed with no replacement.
+ Note that the vulnerability mentioned in LOGBACK-1591 requires
write access to logback's configuration file as a
prerequisite. The log4Shell/CVE-2021-44228 and LOGBACK-1591
are of different severity levels. A successful RCE requires
all of the following conditions to be met:
- write access to logback.xml
- use of versions lower then 1.2.8
- reloading of poisoned configuration data, which implies
application restart or scan='true' set prior to attack
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.3 | logback | 1.2.8-3.3.1 |
Vulnerabilities 1
-
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