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.
References
Link | Resource |
---|---|
http://www.openwall.com/lists/oss-security/2022/01/18/4 | Mailing List Third Party Advisory |
https://lists.apache.org/thread/pt6lh3pbsvxqlwlp4c5l798dv2hkc85y | Issue Tracking Mailing List Vendor Advisory |
https://logging.apache.org/log4j/1.2/index.html | Vendor Advisory |
https://security.netapp.com/advisory/ntap-20220217-0007/ | Third Party Advisory |
https://www.oracle.com/security-alerts/cpuapr2022.html | Patch Third Party Advisory |
https://www.oracle.com/security-alerts/cpujul2022.html | Patch Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: apache
Published: 2022-01-18T15:25:22
Updated: 2022-07-25T16:49:18
Reserved: 2022-01-17T00:00:00
Link: CVE-2022-23305
JSON object: View
NVD Information
Status : Analyzed
Published: 2022-01-18T16:15:08.350
Modified: 2023-02-24T15:30:38.993
Link: CVE-2022-23305
JSON object: View
Redhat Information
No data.
CWE