CVE-2023-31038
published 2023-05-08CVE-2023-31038: 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…
PriorityP351high8.8CVSS 3.1
AVNACLPRLUINSUCHIHAH
EPSS
1.60%
72.9th percentile
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:
... other params here ...
The migrated configuration snippet with new ColumnMapping parameters:
... other params here ...
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | log4cxx | >= 0 < 1.1.0-1 | 1.1.0-1 |
| apache | log4cxx | >= 0 < 1.1.0-1 | 1.1.0-1 |
| apache | log4cxx | >= 0.9.0 < 1.1.0 | 1.1.0 |
| apache_software_foundation | apache_log4cxx | >= 0.9.0 < 1.1.0 | 1.1.0 |
| debian | log4cxx | < log4cxx 1.1.0-1 (forky) | log4cxx 1.1.0-1 (forky) |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv8.8HIGH
vendor_debian8.8LOW
vendor_redhat8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
log4cxx: SQL injection in Log4cxx when using the ODBC appender to send log messages to a database
vendor_redhat·2023-05-07·CVSS 8.8
CVE-2023-31038 [HIGH] CWE-89 log4cxx: SQL injection in Log4cxx when using the ODBC appender to send log messages to a database
log4cxx: SQL injection in Log4cxx when using the ODBC appender to send log messages to a database
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. OD
Debian
CVE-2023-31038: log4cxx - SQL injection in Log4cxx when using the ODBC appender to send log messages to a ...
vendor_debian·2023·CVSS 8.8
CVE-2023-31038 [HIGH] CVE-2023-31038: log4cxx - SQL injection in Log4cxx when using the ODBC appender to send log messages to a ...
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 logge
GHSA
GHSA-76cx-3v2m-9952: SQL injection in Log4cxx when using the ODBC appender to send log messages to a database
ghsa_unreviewed·2023-07-06
CVE-2023-31038 [HIGH] CWE-89 GHSA-76cx-3v2m-9952: SQL injection in Log4cxx when using the ODBC appender to send log messages to a database
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
OSV
CVE-2023-31038: SQL injection in Log4cxx when using the ODBC appender to send log messages to a database
osv·2023-05-08·CVSS 8.8
CVE-2023-31038 [HIGH] CVE-2023-31038: SQL injection in Log4cxx when using the ODBC appender to send log messages to a database
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 logge
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2023-05-08
Published