Affected versions of this package are vulnerable to Arbitrary Code Execution. Note: Even though this vulnerability appears to be related to the log4Shell vulnerability, this vulnerability requires an attacker to have access to modify configurations to be exploitable, which is rarely possible.
An attacker with access to modification of logging configuration is able to configure JDBCAppender with a data source referencing a JNDI URI - which can execute malicious code.
In the fixed versions, JDBCAppender is using JndiManager and disables JNDI lookups by default (via log4j2.enableJndiJdbc=false).
Alternative Remediation
If you have reason to believe your application may be vulnerable and upgrading is not an option, you can either:
Disable/remove JDBCAppender
If JDBCAppender is used, make sure that it is not configured to use any protocol other than Java
Remediation
Upgrade org.apache.logging.log4j:log4j-core to version 2.3.2, 2.12.4, 2.17.1 or higher.
Overview
org.apache.logging.log4j:log4j-core is a logging library for Java.
Affected versions of this package are vulnerable to Arbitrary Code Execution.
Note: Even though this vulnerability appears to be related to the log4Shell vulnerability, this vulnerability requires an attacker to have access to modify configurations to be exploitable, which is rarely possible.
An attacker with access to modification of logging configuration is able to configure
JDBCAppenderwith a data source referencing a JNDI URI - which can execute malicious code.In the fixed versions,
JDBCAppenderis usingJndiManagerand disables JNDI lookups by default (vialog4j2.enableJndiJdbc=false).Alternative Remediation
If you have reason to believe your application may be vulnerable and upgrading is not an option, you can either:
JDBCAppenderJDBCAppenderis used, make sure that it is not configured to use any protocol other than JavaRemediation
Upgrade
org.apache.logging.log4j:log4j-coreto version 2.3.2, 2.12.4, 2.17.1 or higher.References