An update for log4j12 is now available for openEuler-20.03-LTS-SP1 and openEuler-20.03-LTS-SP3 Security Advisory openeuler-security@openeuler.org openEuler security committee openEuler-SA-2022-1781 Final 1.0 1.0 2022-07-26 Initial 2022-07-26 2022-07-26 openEuler SA Tool V1.0 2022-07-26 log4j12 security update An update for log4j12 is now available for openEuler-20.03-LTS-SP1 and openEuler-20.03-LTS-SP3. With log4j it is possible to enable logging at runtime without modifying the application binary. Security Fix(es): 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) An update for log4j12 is now available for openEuler-20.03-LTS-SP1 and openEuler-20.03-LTS-SP3. openEuler Security has rated this update as having a security impact of critical. A Common Vunlnerability Scoring System(CVSS)base score,which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section. Critical log4j12 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-1781 https://www.openeuler.org/en/security/cve/detail.html?id=CVE-2022-23305 https://nvd.nist.gov/vuln/detail/CVE-2022-23305 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 log4j12-1.2.17-25.oe1.noarch.rpm log4j12-help-1.2.17-25.oe1.noarch.rpm log4j12-help-1.2.17-25.oe1.noarch.rpm log4j12-1.2.17-25.oe1.noarch.rpm log4j12-1.2.17-25.oe1.src.rpm log4j12-1.2.17-25.oe1.src.rpm 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. 2022-07-26 CVE-2022-23305 openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 Critical 9.8 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H log4j12 security update 2022-07-26 https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-1781