Severity: 6.8
Affected versions:
- Apache Log4cxx 0.9.0 before 1.1.0
Description:
SQL injection in Log4cxx when using the ODBC appender to send log messages to a
database. No fields sent to the database were properly escaped for SQL
injection. This has been the case since at least version 0.9.0(released
2003-08-06)
Note that Log4cxx is a C++ framework, so only C++ applications are affected.
Before version 1.1.0, the ODBC appender was automatically part of Log4cxx if
the library was found when compiling the library. As of version 1.1.0, this
must be both explicitly enabled in order to be compiled in.
Three preconditions must be met for this vulnerability to be possible:
1. Log4cxx compiled with ODBC support(before version 1.1.0, this was
auto-detected at compile time)
2. ODBCAppender enabled for logging messages to, generally done via a config
file
3. User input is logged at some point. If your application does not have user
input, it is unlikely to be affected.
Users are recommended to upgrade to version 1.1.0 which properly binds the
parameters to the SQL statement, or migrate to the new DBAppender class which
supports an ODBC connection in addition to other databases.
Note that this fix does require a configuration file update, as the old
configuration files will not configure properly. An example is shown below,
and more information may be found in the Log4cxx documentation on the
ODBCAppender.
Example of old configuration snippet:
<appender name="SqlODBCAppender" class="ODBCAppender">
<param name="sql" value="INSERT INTO logs (message) VALUES ('%m')" />
... other params here ...
</appender>
The migrated configuration snippet with new ColumnMapping parameters:
<appender name="SqlODBCAppender" class="ODBCAppender">
<param name="sql" value="INSERT INTO logs (message) VALUES (?)" />
<param name="ColumnMapping" value="message"/>
... other params here ...
</appender>
Required Configurations:
Log4cxx must be built with ODBC support, and configured to log messages to a
database for this to occur
References:
https://logging.apache.org/
https://www.cve.org/CVERecord?id=CVE-2023-31038
