Описание
Security update for logback
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
Список пакетов
openSUSE Leap 15.3
Ссылки
- E-Mail link for openSUSE-SU-2021:4109-1
- SUSE Security Ratings
- SUSE Bug 1193795
- SUSE CVE CVE-2021-44228 page
Описание
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 can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
Затронутые продукты
Ссылки
- CVE-2021-44228
- SUSE Bug 1193611
- SUSE Bug 1193662
- SUSE Bug 1193743
- SUSE Bug 1193795
- SUSE Bug 1194016
- SUSE Bug 1194123
- SUSE Bug 1202994