Vendororacle, netapp, broadcom, apache, qosProductbusiness intelligence, jdeveloper, communications unified inventory management, snapmanager, hyperion data relationship management, business process management suite, healthcare foundation, communications instant messaging server, enterprise manager base platform, communications network integrity, mysql enterprise monitor, identity manager connector, communications messaging server, hyperion infrastructure technology, financial services revenue management and billing analytics, brocade sannav, communications offline mediation controller, middleware common libraries and tools, advanced supply chain planning, log4j, reload4j, communications eagle ftp table base retrieval, e-business suite cloud manager and cloud backup module, identity management suite, e-business suite information discoveryDiscoveredJan 18, 2022UpdatedMay 27, 2026
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…