remkop edited a comment on pull request #608: URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126
> Hi @rgoers, is log4j 1.x vulnerable? Hi @yuezk, as far as I can tell, log4j 1.x does not support lookups. ~~I also could not find any other reference to JNDI in the [log4j 1.x source code](http://svn.apache.org/viewvc/logging/log4j/trunk/). So, no guarantees but it looks like 1.x is not impacted by this vulnerability.~~ **_CORRECTION_**: **log4j 1.x contains a JMS Appender which can use JNDI. So I would say that, yes, log4j 1.x is also impacted by this vulnerability** (Thank you @garydgregory for pointing this out). **Update (2021-12-11 09:09 JST): according to [this analysis](https://twitter.com/ceki/status/1469449618316533762) by @ceki (the author of log4j 1.x), Log4j 1.x is not impacted, since it does not have lookups, and the JMS Appender only loads Strings from the remote server, not serialized objects.** **Update (2021-12-12 10:09 JST): according to [this analysis](https://github.com/apache/logging-log4j2/pull/608#issuecomment-991723301) by @TopStreamsNet, strictly speaking, applications using Log4j 1.x may be impacted if their configuration uses JNDI. However, the risk is much lower.** Note that log4j 1.x is [End of Life](https://logging.apache.org/log4j/1.2/) and has [other security vulnerabilities](https://www.cvedetails.com/cve/CVE-2019-17571/) that will not be fixed. ~~So we do not recommend using log4j 1.x as a way to avoid this security vulnerability.~~ The recommendation is to upgrade to 2.15.0. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
