albfernandez / log4j

Mirror of Apache log4j

Hi there 👋

log4j's Issues

CVE-2021-44228 -> please remove JMSAppender for log4j 1.2.7

Reading

https://lists.apache.org/thread/lgbtvvmy68p0059yoyn9qxzosdmx4jdv
and

I conclude that log4j 1.2.7 is not directly vulnerable to CVE-2021-44228 .

However
http://slf4j.org/log4shell.html
describes a less easy to exploit potential vulnerability related to the JMSAppender and a JNDI lookup.

As this CVE is currently receiving a lot of attention, it seems best to to address that vulnerability in log4j 1.2.7 to put the mind of our customers at ease completely.

Simply removing the JMSAppender class seems sufficient I think.

CVE-2022-23305 SQL injection in JDBCAppender

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.

Remove dependency on jakarta-oro

Enable java17 in maven github actions

Migrate from travis to Github CI