remkop edited a comment on pull request #608: URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-990758663
> @remkop , thanks for your reply. Just want to make it more clear, because many people reach this issue mainly for the "JNDI lookup" CVE, so, for log4j 1.x, although it contains JMS Appender. But if the "JMS Appender" is not used for log4j 1.x (the usage of JMS Appender is rare), then, it should be not affected by this vulnerable RCE, is this correct? > > > To summarize: Log4j 1.x is also impacted, and we recommend using Log4j 2.15.0 instead. @Baoqi Okay, let me be very clear: Log4j 1.x became [End of Life](https://logging.apache.org/log4j/1.2/) 6 years ago! Anyone who wants to continue using it can do their own risk assessment. :-) **Update (2021-12-11 09:11 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.** -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
