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.
| Version | Base score | Base severity | Vector |
|---|
| Hyperlink | Resource Type |
|---|
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.
| Version | Base score | Base severity | Vector |
|---|
| CAPEC ID | Description |
|---|
Users should upgrade to Log4j 2 or remove usage of the JDBCAppender from their configurations.
| Event | Date |
|---|
| Hyperlink | Resource |
|---|---|
| https://logging.apache.org/log4j/1.2/index.html | x_refsource_MISC |
| https://lists.apache.org/thread/pt6lh3pbsvxqlwlp4c5l798dv2hkc85y | x_refsource_MISC |
| http://www.openwall.com/lists/oss-security/2022/01/18/4 | mailing-list x_refsource_MLIST |
| https://www.oracle.com/security-alerts/cpuapr2022.html | x_refsource_MISC |
| https://security.netapp.com/advisory/ntap-20220217-0007/ | x_refsource_CONFIRM |
| https://www.oracle.com/security-alerts/cpujul2022.html | x_refsource_MISC |
| Version | Base score | Base severity | Vector |
|---|
| CAPEC ID | Description |
|---|
| Event | Date |
|---|
| Hyperlink | Resource |
|---|---|
| https://logging.apache.org/log4j/1.2/index.html | x_refsource_MISC x_transferred |
| https://lists.apache.org/thread/pt6lh3pbsvxqlwlp4c5l798dv2hkc85y | x_refsource_MISC x_transferred |
| http://www.openwall.com/lists/oss-security/2022/01/18/4 | mailing-list x_refsource_MLIST x_transferred |
| https://www.oracle.com/security-alerts/cpuapr2022.html | x_refsource_MISC x_transferred |
| https://security.netapp.com/advisory/ntap-20220217-0007/ | x_refsource_CONFIRM x_transferred |
| https://www.oracle.com/security-alerts/cpujul2022.html | x_refsource_MISC x_transferred |
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.
| Date Added | Due Date | Vulnerability Name | Required Action |
|---|---|---|---|
| N/A |
| Type | Version | Base score | Base severity | Vector |
|---|---|---|---|---|
| Primary | 3.1 | 9.8 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Primary | 2.0 | 6.8 | MEDIUM | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| Hyperlink | Source | Resource |
|---|---|---|
| http://www.openwall.com/lists/oss-security/2022/01/18/4 | security@apache.org | Mailing List Third Party Advisory |
| https://lists.apache.org/thread/pt6lh3pbsvxqlwlp4c5l798dv2hkc85y | security@apache.org | Issue Tracking Mailing List Vendor Advisory |
| https://logging.apache.org/log4j/1.2/index.html | security@apache.org | Vendor Advisory |
| https://security.netapp.com/advisory/ntap-20220217-0007/ | security@apache.org | Third Party Advisory |
| https://www.oracle.com/security-alerts/cpuapr2022.html | security@apache.org | Patch Third Party Advisory |
| https://www.oracle.com/security-alerts/cpujul2022.html | security@apache.org | Patch Third Party Advisory |