FranciscoBorges commented on pull request #34895: URL: https://github.com/apache/spark/pull/34895#issuecomment-995885724
@srowen Hello, Thank you for your answer. Let me try to back it up: Log4J 1.X is affected even though it requires a specifically problematic configuration in place (usage of JMSAppender). See <https://access.redhat.com/security/cve/CVE-2021-4104> and <https://bugzilla.redhat.com/show_bug.cgi?id=2031667>. Now I appreciate that the scope is much narrower than _CVE-2021-44228_, but I still did rather not have Log4J 1.X running anywhere. Specially in the light of statements like https://logging.apache.org/log4j/2.x/security.html > Please note that Log4j 1.x has reached end of life and is no longer supported. Vulnerabilities reported after August 2015 against Log4j 1.x were not checked and will not be fixed. Users should upgrade to Log4j 2 to obtain security fixes. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
