NetSight
kritisch9.8

CVE-2022-23305

SQL Injection in Log4j 1.2.x

Auswirkung

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.

Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, ohne Anmeldung, ohne Zutun eines Nutzers. Bei Erfolg: hohes Risiko, dass Daten ausgelesen werden, hohes Risiko, dass Daten oder Systeme verändert werden, hohes Risiko für Ausfälle.

Betroffene Pakete

ÖkosystemPaketBetroffenBehoben in
mavenlog4j:log4j<= 1.2.17nicht erfasst
mavenorg.zenframework.z8.dependencies.commons:log4j-1.2.17<= 2.0nicht erfasst

Betroffene Produkte

HerstellerProduktBetroffene Versionen
ApacheLog4j
ab 1.2 bis einschließlich 1.2.17
BroadcomBrocade Sannav
Alle Versionen
NetappSnapmanager
Alle Versionen
OracleAdvanced Supply Chain Planning
Versionen 12.1, 12.2
OracleBusiness Intelligence
Versionen 5.9.0.0.0, 12.2.1.3.0, 12.2.1.4.0
OracleBusiness Process Management Suite
Versionen 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
vor 12.0.0.4.4
Version 12.0.0.5.0
QosReload4j
vor 1.2.18.2

Schwachstellenklasse

Referenzen