linux-ops edited a comment on pull request #608: URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-990629440
> > 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). > > 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. Do anyone know if I depends on the following 2: - org.apache.logging.log4j:log4j-api - org.apache.logging.log4j:log4j-to-slf4jBut without dependency on - org.apache.logging.log4j:log4j-corein this situation, is this safe from this RCE? Thanks.Edit, This may affect both log4j 2.x and log4j 1.x (see comments bellow, thanks.)reply agwa 1 hour ago \| parent \| next [–]> By the way. This only affect log4j 2.x (https://github.com/apache/logging-log4j2). the log4j 1.x (https://github.com/apache/log4j) is not affected.That's not what https://github.com/apache/logging-log4j2/pull/608#issuecomme... saysreply Link:https://news.ycombinator.com/item?id=29504755 @remkop Which description is correct ? -- 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
