NetSight
IP …
critical9.8

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 PatternLay…

Impact

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.

Affected products

VendorProductAffected versions
ApacheLog4j
from 1.2 through 1.2.17
NetappSnapmanager
All versions
BroadcomBrocade Sannav
All versions
QosReload4j
before 1.2.18.2
OracleAdvanced Supply Chain Planning
Versions 12.1, 12.2
OracleBusiness Intelligence
Versions 5.9.0.0.0, 12.2.1.3.0, 12.2.1.4.0
OracleBusiness Process Management Suite
Versions 12.2.1.3.0, 12.2.1.4.0
OracleCommunications Eagle Ftp Table Base Retrieval
Version 4.5
OracleCommunications Instant Messaging Server
Version 10.0.1.5.0
OracleCommunications Messaging Server
Version 8.1
OracleCommunications Network Integrity
Version 7.3.6
OracleCommunications Offline Mediation Controller
before 12.0.0.4.4
Version 12.0.0.5.0

Weakness classification

CWE-89

References