Описание
Security update for log4j
This update for log4j fixes the following issues:
- CVE-2022-23307: Fixed deserialization flaw in the chainsaw component of log4j leading to malicious code execution. (bsc#1194844)
- CVE-2022-23305: Fixed SQL injection when application is configured to use JDBCAppender. (bsc#1194843)
- CVE-2022-23302: Fixed remote code execution when application is configured to use JMSSink. (bsc#1194842)
Список пакетов
SUSE Linux Enterprise Point of Sale 11 SP3
SUSE Linux Enterprise Server 11 SP4-LTSS
Ссылки
- Link for SUSE-SU-2022:14881-1
- E-Mail link for SUSE-SU-2022:14881-1
- SUSE Security Ratings
- SUSE Bug 1194842
- SUSE Bug 1194843
- SUSE Bug 1194844
- SUSE CVE CVE-2022-23302 page
- SUSE CVE CVE-2022-23305 page
- SUSE CVE CVE-2022-23307 page
Описание
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, 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-2022-23302
- SUSE Bug 1194842
Описание
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. 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-2022-23305
- SUSE Bug 1194843
- SUSE Bug 1196392
- SUSE Bug 1225673
Описание
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
Затронутые продукты
Ссылки
- CVE-2022-23307
- SUSE Bug 1194844