CVE-2022-23305

CRITICALCVSS 9.8/10EPSS 66.54%

Last modified

CVE-2022-23305 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 66.54% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
9.8/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
66.54%

99.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
ApacheLog4j>= 1.2, <= 1.2.17
NetappSnapmanagerAll versions
BroadcomBrocade SannavAll versions
QosReload4j< 1.2.18.2
OracleAdvanced Supply Chain Planning12.1
OracleAdvanced Supply Chain Planning12.2
OracleBusiness Intelligence5.9.0.0.0
OracleBusiness Intelligence12.2.1.3.0
OracleBusiness Intelligence12.2.1.4.0
OracleBusiness Process Management Suite12.2.1.3.0
OracleBusiness Process Management Suite12.2.1.4.0
OracleCommunications Eagle Ftp Table Base Retrieval4.5
OracleCommunications Instant Messaging Server10.0.1.5.0
OracleCommunications Messaging Server8.1
OracleCommunications Network Integrity7.3.6
OracleCommunications Offline Mediation Controller< 12.0.0.4.4
OracleCommunications Offline Mediation Controller12.0.0.5.0
OracleCommunications Unified Inventory Management7.4.1
OracleCommunications Unified Inventory Management7.4.2
OracleE-Business Suite Cloud Manager And Cloud Backup Module< 2.2.1.1.1
OracleE-Business Suite Cloud Manager And Cloud Backup Module2.2.1.1.1
OracleE-Business Suite Information Discovery>= 12.2.3, <= 12.2.11
OracleEnterprise Manager Base Platform13.4.0.0
OracleEnterprise Manager Base Platform13.5.0.0
OracleFinancial Services Revenue Management And Billing Analytics2.7.0.0
OracleFinancial Services Revenue Management And Billing Analytics2.7.0.1
OracleFinancial Services Revenue Management And Billing Analytics2.8.0.0
OracleHealthcare Foundation8.1.0
OracleHyperion Data Relationship Management< 11.2.8.0
OracleHyperion Infrastructure Technology< 11.2.8.0
OracleIdentity Management Suite12.2.1.3.0
OracleIdentity Management Suite12.2.1.4.0
OracleIdentity Manager Connector11.1.1.5.0
OracleJdeveloper12.2.1.3.0
OracleMiddleware Common Libraries And Tools12.2.1.4.0
OracleMysql Enterprise Monitor<= 8.0.29
OracleRetail Extract Transform And Load13.2.5
OracleTuxedo12.2.2.0.0
OracleWeblogic Server12.2.1.3.0
OracleWeblogic Server12.2.1.4.0
OracleWeblogic Server14.1.1.0.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2022-23305?
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.
How severe is CVE-2022-23305?
CVE-2022-23305 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 66.54% probability of exploitation in the next 30 days.
How do I fix CVE-2022-23305?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2022-23305?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST