[ https://issues.apache.org/jira/browse/IGNITE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463120#comment-17463120 ]
Ivan Daschinsky edited comment on IGNITE-13464 at 12/21/21, 10:45 AM: ---------------------------------------------------------------------- [~RyzhovSV] [~sdarlington] Ignite zookeper depends on curator framework and use good ole log4j 1.2.17. Removing log4j here is not an option. And I don't understand why, because nothing related with log4j 2 hysteria was (Author: ivandasch): [~RyzhovSV] [~sdarlington] Ignite zookeper depends on curator framework and use good ole log4j 1.7. Removing log4j here is not an option. And I don't understand why, because nothing related with log4j 2 hysteria > Ignite-rest-http, zookeeper modules includes vulnerable dependencies > -------------------------------------------------------------------- > > Key: IGNITE-13464 > URL: https://issues.apache.org/jira/browse/IGNITE-13464 > Project: Ignite > Issue Type: Bug > Components: rest > Affects Versions: 2.9, 2.8.1 > Reporter: Stephen Darlington > Assignee: Sergei Ryzhov > Priority: Blocker > Fix For: 2.12 > > Time Spent: 10m > Remaining Estimate: 0h > > The ignite-rest-http, zookeeper module includes a [vulnerable > version|https://nvd.nist.gov/vuln/detail/CVE-2019-17571] of the log4j > library. It also appears to include slf4j. Why does the REST API include its > own logging libraries? > This was spotted in 2.8.1 but still appears to be an issue in master and 2.9. > More here: > http://apache-ignite-users.70518.x6.nabble.com/critical-security-vulnerability-for-opt-ignite-apache-ignite-libs-optional-ignite-rest-http-log4j-1-r-td34031.html -- This message was sent by Atlassian Jira (v8.20.1#820001)